A Cross-Chain Swap Is Pending: What to Check

A cross-chain swap touches two blockchains, so “pending” can describe more than one stage. First check whether the transaction on the source chain has confirmed; that tells you whether the swap has started moving funds out of your wallet.

Open the swap’s status screen and find the source transaction hash, then check it on the source chain’s block explorer. A wallet that still says “pending” may mean the transaction has not been included in a block yet. If the source transaction is confirmed, the wait may be in the bridge or destination step instead. For a related look at route selection, read how QuickSwap picks a wallet route; the route affects which steps a swap may take.

Why is my cross-chain swap still pending?

A cross-chain swap is a sequence of actions across networks, not one transaction that completes everywhere at once. The source transaction can confirm while a bridge message is still being relayed, or while the destination chain is waiting to execute the final swap.

That gap is why a source-chain confirmation does not prove the destination tokens have arrived. The bridge may need to observe the source transaction, pass a message between networks and complete a destination transaction. Network load, confirmation requirements and the route itself can affect how long those steps take.

Use the status label as a clue, not a diagnosis. Interfaces use different wording, but a wallet prompt usually points to source-chain submission; “bridging” or “processing” often means the source step is done and the cross-chain leg is underway. A destination transaction hash gives you another concrete step to check on that chain’s explorer.

What should I check before doing anything?

Compare the status screen with both chain explorers before you retry. Start with the source transaction: if it is still pending, the bridge may not have received anything to process. If it has confirmed, look for a bridge status or destination transaction instead of submitting the same swap again.

1. Copy the source transaction hash from your wallet or the swap interface. Confirm that it belongs to the correct network and check whether it is pending, confirmed or failed.
2. Return to the swap’s original status page using your saved tab or the site you used to start the transaction. Check its latest status and any destination transaction hash.
3. If there is a destination hash, open it on the destination chain’s explorer. Check whether it succeeded, failed or is still pending.
4. Compare the destination wallet address, chain and token with the swap details. If the swap says it completed but the token is not visible, check the wallet on the destination network and confirm that it is displaying the right token.

Keep the hashes and screenshots of the status details if you later need support. They help identify which leg is waiting. A missing balance in one wallet view does not by itself show that the transaction failed; the asset may be on a different network or may need to be added to the wallet’s token display.

Should I retry, speed up or cancel the swap?

Only consider a wallet replacement or cancellation when the source transaction itself is still pending. On some networks, a wallet can offer a speed-up or cancellation that replaces a pending transaction using the same account sequence or nonce. The wallet’s instructions and network rules govern whether that is available; do not send a second swap just because the interface has not updated.

If the source transaction is confirmed, a speed-up in your wallet will not make the bridge or destination step complete. Use the original swap’s status page and its official recovery instructions. Depending on the route, recovery may mean waiting for an automatic retry or refund, or following a specific claim process. Do not assume a refund will return the same token or arrive on the same chain you started from; check the route’s recovery details.

A short checklist helps keep the diagnosis grounded:

• Source transaction pending: check its wallet status and explorer record.
• Source transaction confirmed: check the bridge or swap status for the next step.
• Destination transaction failed: follow the route provider’s recovery instructions.
• Completed status, missing token: check the destination network and token display.

When should I contact support?

Contact the swap or bridge provider through the official site when its status page stops updating, reports a failure without clear recovery steps, or marks the transfer complete but the destination explorer does not show the expected result. Give support the source hash, any destination hash, both networks and the status text. Never share your seed phrase or private key; support does not need either to investigate a transaction.

The practical rule is simple: trace the swap one leg at a time. Confirm the source transaction, check the bridge status, then verify the destination. Retry only when the status and the route’s instructions say a retry is appropriate.