Four Checks to Make on a Pending Cross-Chain Swap

A pending cross-chain swap should be checked at four points: the source transaction, bridge transfer, destination execution and final token balance. A swap can finish on the sending chain while the receiving-chain transaction is still waiting, so one “pending” label may hide several different stages.

What should you check first?

Check the source-chain transaction hash in that chain’s block explorer. Confirm whether it is pending, successful or failed, and compare the token and amount sent with the swap details; a successful receipt shows that the first step completed, not that the destination tokens arrived.

Cross-chain swaps usually involve a source transaction followed by a message or asset transfer and a destination transaction. For a fuller walkthrough, see this Biswap cross-chain swap flow and its transaction stages. The key distinction is whether the source step has completed and the destination step has been submitted.

How can you tell where the swap is waiting?

Match the swap’s route and transaction details to the status shown for each stage. Check these four items:

• Source receipt: Was the transaction confirmed, or did it fail or remain pending?
• Bridge or message status: Does the route show that the transfer or message was detected and processed?
• Destination transaction: Is there a receiving-chain hash, and does its explorer show success, pending or failure?
• Final balance: Does the destination wallet show the expected token, including any difference between the quoted and received amount?

If the source receipt succeeded but no destination transaction appears, the delay is likely between those two steps. If the destination transaction failed, inspect its status and any displayed reason before deciding whether a retry is possible; sending the swap again without checking can create a second transaction.

When is a pending swap complete?

Treat the swap as complete when the destination transaction succeeds and the receiving wallet’s balance reflects the output. A quote or “submitted” screen records an expected route or an initiated action; it does not by itself confirm delivery.

Use the transaction hash from the stage that is still waiting, and check that chain’s explorer for its latest status. If the interface and explorer disagree, the explorer’s recorded transaction state is the useful next signal; once the destination hash shows success, check the wallet balance again.