How to Check Which Token Arrives After a Cross-Chain Swap

To check which token arrives after a cross-chain swap, read the destination network and output token in the route, then verify the completed destination transaction and token contract. The route begins when you approve or send the input token on the source chain. A router contract may swap it there, pass it to a bridge or messaging system, and trigger another swap or transfer on the destination chain. The token shown in the quote is the intended output; only the completed destination step shows what was delivered.

Think of the route as a parcel with a handoff: the source transaction starts the trip, but the destination receipt confirms the contents. A swap route and an exchange withdrawal can both show a destination asset while using different delivery steps. For more detail on Biswap route and exchange withdrawal checks before sending, see the separate guide. Here, the key is to match the final token to the destination network, rather than relying on a familiar symbol.

Where does the route show the token you should expect?

The route’s destination or “To” field names the network and token the swap is designed to deliver. Check both before signing: “USDC,” for example, is not enough on its own, because token symbols can be reused and a token on one chain is not automatically the same asset on another. Open the token details in the quote and note its contract address. If the route lists intermediate tokens, focus on the final output, not the asset used between chains.

Read the quoted amount as an estimate subject to the route’s execution conditions. The route may combine a source-chain swap, a cross-chain transfer and a destination-chain swap. Each step has its own contract and can have a separate transaction record. The quote describes the plan; it does not prove that every step completed or that the final amount exactly matched the estimate.

How can you verify what arrived on the destination chain?

First, find the swap’s status or tracking page using the source transaction hash or route identifier. The source chain’s explorer can confirm that your input transaction was included, but a successful source transaction alone does not confirm delivery. Look for a destination transaction or a completed status, then open that transaction in the destination chain’s explorer.

Check the destination transaction’s recipient and token transfer details. Match the recipient address to your wallet, and match the token’s contract address to the one shown in the quote or a trusted token listing for that chain. Compare the transferred amount with the route’s final output, allowing for any fees or execution changes the route disclosed. If the wallet balance does not display the token, check the address on the destination explorer; some wallets need the token added before showing it.

A quick check before acting is to confirm:

• The destination network in the route matches the network you intended.
• The final output token’s contract address matches the destination asset you expect.
• The destination transaction completed and names your wallet as recipient.
• The received amount and any displayed fee fit the completed route details.

What if the destination token is different or the swap is still pending?

If the destination step is pending, the source transaction may have completed while the cross-chain message or destination execution is still underway. Use the route’s status page to follow that step; do not treat the source-chain confirmation as proof that the output has arrived. If the destination transaction completed but shows another token, compare its contract address and transfer record with the route details. A matching symbol is not sufficient evidence.

If the route reports failure or an unexpected result, check its stated recovery or refund process before sending another transaction. A cross-chain route can fail at a later step even after the source transaction succeeded, and the next action depends on how that route handles failure. The practical rule is simple: use the quote to identify the intended destination token, then use the destination transaction to identify the token that actually arrived.