Follow a Cross-Chain Swap From Your Wallet to Its Destination

Trace a cross-chain swap by following its source transaction, bridge message and destination transaction. Your wallet shows the first request, but the destination leg may still be running after that.

What identifies each part of a cross-chain swap?

Each leg has its own transaction hash, a unique identifier you can search in a block explorer. Start with the hash in your wallet’s activity view and open it on the explorer for the source network; check that the sender, token and amount match your swap. If the wallet only says pending, see what to do when QuickSwap is pending for that specific situation. A bridge message or transfer record can then connect the source event to a separate destination transaction.

How do you trace the swap step by step?

Follow the records in order, using the same wallet address and token details to confirm that each event belongs to your swap:

1. Open the source transaction and note its status, token transfer, recipient contract and transaction hash.
2. If it succeeded, look for the bridge’s message or transfer record linked to that transaction. The bridge may show whether it has observed or processed the message.
3. Use the destination network and wallet address to find the resulting transaction or token transfer. Confirm the asset and amount; a wrapped token may have a different name or contract address from the source asset.
4. Save each hash and status. If you contact the bridge or swap interface, these records make it easier to identify which leg needs attention.

How can you tell a delay from a failed swap?

A successful source transaction means the source network accepted the transaction; it does not prove the destination transfer is complete. Check the explorer’s status and the bridge’s message state together, since they describe different steps.

• Source pending: the first transaction has not yet been included in a block.
• Source failed: the transaction did not complete successfully; inspect the explorer’s error details.
• Source succeeded, destination missing: the source leg completed, so check the bridge message or its tracker before taking another action.
• Destination succeeded: verify the received token and amount in the destination transaction and your wallet.

The useful distinction is between a transaction and a swap: the explorer reports what happened on one network, while the bridge record helps explain what is happening between networks. Follow the evidence across both before retrying, because submitting a second swap can create a separate transaction rather than resolve the first one.