Reconciling a swap that moved tokens across two different chains

07 September 2026

When tokens move from one chain to another during a swap, reconciling that trade means proving that the asset that left the source chain is the same asset that arrived on the destination chain. You cannot rely on a single transaction hash. You need both sides of the bridge.

Why cross-chain swaps break simple record-keeping

A normal single-chain swap leaves one transaction hash, one block explorer entry, and one clear record of what changed. Cross-chain swaps are different. The swap happens in two separate steps: a lock or burn on the source chain, and a mint or release on the destination chain. No single transaction contains both events. This creates a gap that tax authorities, auditors, or even you months later will struggle to fill if you did not save the right links.

The exchange that routes your trade usually provides a status page or a reference number that ties the two halves together. That reference number is the only document that connects the source-chain transaction to the destination-chain transaction. Without it, you have two orphaned transactions that a third party could reasonably treat as unrelated.

What to save for each half

For the source chain - the chain the tokens left - save the full transaction hash, the block number, and the exact amount and token contract address of what was sent. The block explorer will show a transfer to a bridge contract or a burn address. That alone does not prove the destination chain received anything.

For the destination chain, save the transaction hash of the incoming transfer, the block number, and the amount and token contract address of what arrived. The block explorer will show a mint or a release from a bridge contract. That alone does not prove the source chain sent anything.

The exchange reference number is the bridge between these two halves. Save it alongside both transaction hashes. Without it, reconciling the two halves requires contacting support and hoping their logs still exist.

Timing mismatches and slippage

Cross-chain swaps do not settle at the same second. The source-chain transaction might confirm in seconds. The destination-chain transaction might take minutes or, during congestion, hours. Record the timestamp of each confirmation separately. Do not assume they match. A difference of several hours is normal and does not indicate a problem, but it will confuse any automated reconciliation tool that expects matching timestamps.

The amount that arrives on the destination chain is rarely identical to the amount that left the source chain. Bridge fees, network fees, and slippage all take their cut. Save the exact amounts for both sides. If the destination amount is lower, you need to be able to explain the difference. The exchange reference number usually includes a fee breakdown. Save that too.

What happens if you lose the reference number

Without the reference number, you have two transactions that share no common identifier except the exchange's internal logs. If the exchange does not keep those logs indefinitely, or if it shuts down, you lose the ability to prove the two transactions are connected. A tax authority that sees an outgoing transaction on one chain and an incoming transaction on another chain months later may treat them as separate events, each with its own tax implications. You would then need to argue that they are a single trade, and your evidence is two block explorer links that do not reference each other.

This is why the sibling pages under "What swap records to keep for tax time on Tron" exist. They walk through which specific fields to copy from each chain's block explorer and how to store the exchange reference number in a way that survives browser history wipes. If you have not read those pages, start with "Which swap details should I copy before I close the browser tab." It covers the exact fields that cross-chain swaps require.

A concrete example of the reconciliation process

You send 100 USDT on Tron to a bridge address. The block explorer shows the transfer. You receive 99.2 USDT on Ethereum. The block explorer shows a mint. The exchange reference number, which you saved as a plain text note, contains the source transaction hash, the destination transaction hash, and the fee breakdown. When you later need to prove that these two transactions are the same trade, you present the reference number and both hashes. The reference number is the authoritative link. The block explorer entries are supporting evidence.

If you only saved the source hash, you can show that you sent 100 USDT, but you cannot prove where it went. If you only saved the destination hash, you can show that you received 99.2 USDT, but you cannot prove where it came from. The reference number is the only document that closes the loop.

When to reconcile

Do it immediately after the swap completes. Do not wait until tax season. The exchange status page may disappear. The reference number may expire. The block explorer entries will remain, but without the reference number they are just two unrelated transactions. Save all three pieces - source hash, destination hash, reference number - in the same place. A plain text file, a password manager note, or a spreadsheet all work. The format matters less than the completeness.

If you are reconciling a swap that happened weeks or months ago and you did not save the reference number, check the exchange's order history if you used an account. Some exchanges keep order records for years. If you used a non-custodial interface that does not retain history, you are likely out of luck. The two block explorer entries are all you have, and they will not convince an auditor who understands cross-chain mechanics.

Back to tron