A pending cross-chain swap is a stage problem

A pending cross-chain swap is diagnosed by finding the last stage that completed: the source-chain transaction, the bridge transfer or the destination-chain swap. Before, a single-chain swap usually meant checking one transaction and its receipt; a cross-chain route can involve several transactions and an off-chain relayer or solver. That adds more ways to wait, but it also gives you clues. Check each stage in order, and do not submit the swap again until you know whether the original funds moved.

What does “pending” mean for a cross-chain swap?

“Pending” can describe different stages, so first identify which transaction or status the wallet or route tracker is showing. A wallet may be waiting for the source-chain transaction to be included in a block. Once that transaction confirms, the route can still be in progress while a bridge, relayer or solver handles the transfer. A destination transaction may then be needed to deliver or swap the funds.

This differs from a simple swap, where a confirmed transaction usually completes the exchange in one chain. Cross-chain aggregators can assemble routes that combine a source swap, a bridge and a destination swap; a bridge itself may also use different transfer and settlement steps. The tracker’s overall “pending” label can hide which part is waiting. For the extra detail behind that distinction, see this fuller Paraswap guide to diagnosing a cross-chain swap. The useful question is not just how long the status has stayed pending, but what the last confirmed event was.

How can you find the stage where the swap stopped?

Start with the source transaction hash, not the wallet’s spinner. Open it in the explorer for the sending chain and confirm that the chain, sender, token and amount match the swap you intended. A transaction marked pending has not yet completed on that chain. If it is confirmed, check its receipt and the route tracker for a bridge or destination reference; a source confirmation does not by itself prove the destination action finished.

Then follow the route’s own status page, if it provides one. Match the source hash or transfer identifier to the route and look for the latest completed step, destination transaction hash, or a reported failure. The stages to distinguish are:

• Source transaction pending: the wallet submitted a transaction, but the source chain has not confirmed it.
• Source confirmed, bridge in progress: the source funds moved, while the cross-chain message or transfer is still being processed.
• Destination transfer complete: the destination token arrived, but a separate swap or contract action may still be outstanding.
• Destination action failed: the route reached the receiving chain, but the final swap or delivery needs investigation under that route’s recovery process.

These labels are not universal. Some routes combine steps, and some trackers update later than the chain explorer. When the tracker and explorer disagree, use the destination transaction hash or transfer identifier to check the relevant chain directly. A confirmed source transaction plus no destination transaction is a different problem from a destination transaction that reverted.

When should you wait, speed up or seek recovery?

Wait when the source transaction has confirmed and the route tracker still shows bridge processing without a failure. Cross-chain completion depends on the route’s settlement design and the participating chains, so a single expected duration does not apply to every swap. Compare the current status with that route’s own estimate or support guidance, rather than treating a delay alone as proof the funds are lost.

If the source transaction itself remains pending, check its status and nonce in the explorer and wallet. A speed-up or cancellation may be possible on some chains, but it concerns that unconfirmed source transaction. It cannot accelerate a bridge transfer after the source transaction has confirmed. Do not send a replacement swap merely because the original screen is still open: the first transaction could later confirm, leaving you with two transfers.

If the route reports a destination failure, use the route provider’s documented recovery path and provide the source hash, route identifier and any destination hash. Recovery differs by bridge and failure type; some routes have a refund or claim process, while others require a separate action. Do not share a seed phrase or sign an unfamiliar “recovery” transaction sent in a message. A legitimate recovery check should be tied to the transaction and route you can independently verify.

The trade-off is between waiting for a route to finish and acting on a transaction that may still be live. Retrying can be faster only when the original source transaction is known not to have executed; otherwise it can duplicate the transfer. The signals worth watching next are the source receipt, the bridge or route status, and the destination receipt. Together, they show whether the swap is still progressing, needs a source-chain adjustment, or has reached a recovery step.