How to Track a Pending Cross-Chain Swap
Track a pending cross-chain swap by checking the source transaction, bridge status and destination wallet, then use the route’s own timeout and refund rules.
Uruguay Can Editorial

Track a pending cross-chain swap by following its source transaction through the bridge and checking whether the destination transaction has completed. A wallet may show “pending” even after your source-chain transaction is confirmed, because the route still needs to verify that transaction and deliver or release the destination asset.
That distinction matters when you use a QuickSwap route: the swap may involve a bridge or other cross-chain service, and each has its own stages. For a separate decision about whether QuickSwap fits a first cross-chain swap, read this guide to choosing QuickSwap for your first swap. To track a transaction already in progress, start with the transaction details rather than submitting it again.
What does “pending” mean in a cross-chain swap?
“Pending” means the full route has not yet reached a completed state, but it does not identify which step is waiting. First, the source chain must include your transaction; then the bridge or relayer must observe and verify it; finally, the destination chain must process the delivery. Some routes use liquidity to provide the destination asset, while others rely on a lock-and-release or minting process. The exact sequence depends on the route.
How do you track each stage?
Use the transaction hash from the swap confirmation and follow the route one step at a time:
- Open the source-chain transaction in that network’s block explorer. Check whether it is pending, confirmed, or failed, and verify the token and amount.
- If it is confirmed, find the bridge or route status shown in the swap interface. A confirmed source transaction can still be awaiting verification or destination processing.
- Look for a destination transaction hash or status. If one is provided, check it in the destination network’s explorer and confirm the tokens arrived in the intended wallet.
- If the route remains incomplete, use its stated timeout and recovery instructions. Keep the source hash and any route identifier; do not assume a second swap will cancel the first.
What should you check before retrying?
Compare the source transaction, route status, and destination wallet on the correct networks. A destination transaction can succeed even if your wallet has not refreshed its token balance, and some tokens may need to be added to the wallet’s display. If the source transaction failed, the swap did not progress from that transaction; if it succeeded but no destination step appears, the route’s own status and recovery process are the useful next checks.
Use the source transaction as your starting point, then follow the route’s evidence to the destination. That gives you a clearer answer than the wallet’s single “pending” label and helps you avoid submitting a duplicate while the original swap is still processing.