How to Check a Cross-Chain Swap That Has Not Arrived

If you sent a cross-chain swap and cannot see the output yet, check the source transaction first, then trace its destination step. A confirmed source transaction does not always mean the other chain has finished the swap.

Check what happened on the source chain

A transaction hash is the unique code for a transaction; use it to find the record on the source chain’s block explorer, a site that lists chain activity. If the record says “failed” or “reverted,” the swap did not complete there. Check your wallet balance before trying again, especially if you approved token spending in a separate transaction.

If the source transaction succeeded, the route may still need time to confirm it and carry out the destination step. Biswap is a cross-chain bridge and swap service, so it is an example of a service that handles both moving and exchanging assets. The same source-to-destination check applies to a Biswap swap.

The Ethereum.org explanation of transaction finality shows why a transaction may need time before a network treats it as settled. Timing varies by chain and route, so a pending status alone does not tell you that funds are lost.

Trace the destination step before acting

Once the source transaction succeeded, check whether the destination chain recorded the expected token at your receiving address. biswap.uk can handle a cross-chain move and swap as one service. Compare the destination token and address with what you intended to receive.

1. Copy the source transaction hash from your wallet’s activity.
2. Open the source chain’s block explorer and look for its result. Confirm the sending address and token match your transaction.
3. Check the service’s transaction record, if available, for a status showing that destination processing is still underway or complete.
4. Search the destination chain’s explorer for your receiving address and expected token. A successful destination transaction is stronger evidence of delivery than a wallet display alone.

For example, Arbitrum documents cross-chain messages that are submitted on one chain and executed separately on another. Some can need a later retry if automatic execution fails, so a successful source record and a missing destination record can describe an unfinished step, not a failed send.

If the source succeeded but you cannot find a destination record, keep the hash and avoid sending a second swap until you know the first route’s status. If the destination record succeeded but your wallet still looks empty, check that the wallet is viewing the right network and token. The key is to confirm each chain’s step before deciding what to do next.