How to Diagnose a Pending or Failed Cross-Chain Swap

When you submit a cross-chain swap, the protocol processes the amount you approved on the source chain, then waits for the destination step to finish. A delay does not by itself mean the funds are lost: the transfer may be waiting for confirmation, a bridge message or a destination-chain action. Start with the source transaction hash and check what happened at each step.

How do you check where a cross-chain swap is stuck?

Use the transaction hash from the chain where you sent the funds to find the swap in the service’s official explorer. The source-chain explorer can show whether that transaction was accepted, failed or is still waiting to be included; the bridge’s explorer can show what happened after it was accepted. The hash may not identify the destination transaction, so follow the linked transfer details where available.

Read the status before taking action. For Mayan swaps, the Explorer API reports INPROGRESS, COMPLETED or REFUNDED, and uses the source transaction hash to look up the swap. The mayan bridge overview gives more background on how the service moves and swaps assets across chains.

If the source transaction is still pending, check its status on that chain rather than relying on a wallet spinner. If it succeeded but the swap remains in progress, the source step completed and the remaining work is elsewhere in the route. Save the hash, source and destination networks, token names, amount and recipient address; these details make it easier to check the transfer or ask the service’s official support channel for help.

What does pending, failed or refunded mean?

Pending can refer to different stages, so the explorer status matters more than the label in your wallet. A source transaction may be waiting for confirmation, or the source may already be complete while a bridge message, swap or destination delivery is still underway.

Failed can mean the source transaction itself reverted, or that a later step could not complete. If the source transaction failed on-chain, the explorer should show that result; the transaction’s input generally was not transferred by that failed transaction, though network fees may still have been charged. If the source transaction succeeded, do not assume the whole swap failed just because the output has not arrived.

Refunded means the input is being returned or has been returned under the route’s refund process. Check the source-chain wallet and the explorer’s transaction details, including the refund transaction if one is listed. A refund may take another on-chain transaction, so its status can differ from the original swap’s status.

What should you do before retrying a swap?

Confirm the source transaction’s final status first, then check the destination wallet and network. A delivered token can be easy to miss if your wallet is showing another network or does not display that token by default; use the explorer’s destination details to confirm the recipient and token before drawing a conclusion.

• Source pending: Wait for the source chain to resolve the transaction; do not submit the same transfer again while its outcome is unclear.
• Source failed: Check the failure details and available balance before starting a new swap.
• Bridge in progress: Keep the source hash and monitor the official explorer for a completed transfer or refund.
• Refunded or completed: Verify the returned or delivered asset on the relevant chain before making another transfer.

Retrying too early can create a second, separate swap while the first is still moving through the route. Once the explorer shows a final failure or refund, review the reason and confirm the intended token, amount, network and destination address before trying again. Network congestion, route limits or slippage settings can affect whether a swap completes, but the explorer’s record is the starting point for diagnosing this specific transfer.

When should you contact support?

Contact the bridge or swap service through a support route linked from its official site if the source transaction succeeded but the explorer shows no clear completion or refund, or if the displayed recipient or amount appears wrong. Include the transaction hash, both networks, the token and amount, and the status you see; never share your seed phrase or private key.

For most pending swaps, the better first move is to trace the existing transfer, not to send another one. A cross-chain swap has several steps, and checking the source, bridge and destination records in order tells you whether to wait, investigate a failed source transaction or confirm a refund.