You can tell whether a swap is delayed or misdirected by checking its destination transaction, provided you use the right chain explorer. A source-chain receipt only proves that your starting transaction was recorded. The destination side still has to process the transfer or swap.
Start with the transaction record
Find the transaction hash in your wallet’s activity or the service’s transaction history. A transaction hash is the unique code for one on-chain action. Open it in an explorer for the source network, such as Ethereum or Arbitrum; explorers show transaction records for a particular network.
Check that the status says “success” and that the token left your address. “Pending” means the network has not finished recording it. “Failed” means the action did not complete as requested, though a network fee may still have been charged.
A successful source transaction does not always mean the destination tokens have arrived. In many cross-chain systems, the source contract sends a message; a relayer or other service carries it to the destination, where another transaction completes the swap. For the route, price impact, and timing behind that handoff, read what shapes an omnichain swap; this guide focuses on checking the result.
Check the destination network and token
Look for a destination transaction or delivery status in the swap’s tracking details. If there is a destination hash, open it in an explorer for that destination network. Confirm it succeeded and sent tokens to your wallet address.
For example, suppose you swap USDC on Arbitrum for ETH on Base. The source record should show USDC leaving on Arbitrum. The destination record should show ETH reaching your address on Base. Seeing USDC on Arbitrum alone does not prove the swap finished.
If the destination transaction succeeded but your wallet shows no balance, check that the wallet is viewing the destination network. For a token other than its built-in assets, compare the token’s contract address—the identifier for that token on that network—with a trusted project or explorer record. Names and logos can be copied, and the same token can have different contract addresses on different chains.
Know when to wait and when to get help
If the source succeeded but no destination transaction appears, the cross-chain message may still be waiting for verification or delivery. Some systems use a signed message, often called an attestation, as proof that the source action happened. An omnichain route may combine several network actions, so its tracking page can be more useful than either wallet’s activity list.
If tracking says “complete” but the destination record is missing, check the displayed destination address and network first. If both are correct and the status remains unclear, keep the transaction hashes and use the service’s help channel. Never share your recovery phrase or approve a new transaction just to “release” funds.
Practical tip: copy both transaction hashes into your own notes before closing the tracking page.