Five checks for a stuck cross-chain swap

Diagnose a stuck cross-chain swap by checking its source transaction, bridge status and destination receipt in that order. These five checks show whether the delay is in your wallet, the source network, the route provider or the destination network.

How do you confirm the swap started?

Step one is to find the source transaction hash in your wallet’s activity. Open it in the source chain’s block explorer and confirm that the chain, sending address and token match the swap. If the wallet never produced a hash, the transaction may not have been broadcast; check the wallet before submitting again.

Step two is to read the source-chain receipt. A pending receipt means the source network has not included the transaction yet; a failed receipt means the source action reverted. A successful receipt confirms only that source-chain action, not that the destination token has arrived.

Swap costs also vary by route: source gas, bridge fees, destination execution and slippage can affect the quoted amount. For that breakdown, see Fermi Swap’s breakdown of cross-chain costs. The fee estimate can help explain the expected output, but it does not establish where a transfer is in its lifecycle.

Why can a swap pause after source confirmation?

Step three is to check the route provider’s tracker using the source hash or transfer ID. The provider can associate the source transaction with its bridge or solver process and show whether the route is waiting for confirmations, processing a message, attempting destination execution or reporting a failure.

Read the status label alongside its detail and compare it with the source explorer. A generic “pending” label does not identify the delayed stage on its own; the provider’s tracker or status page is the place to check what event it is awaiting.

• Waiting for source confirmations: check the source explorer again after more blocks.
• Waiting for destination transaction: check the provider tracker for a destination hash.
• Failed or reverted: read the reported reason and look for a refund status.
• No transfer found: verify the hash, source chain and route details before contacting support.

Do not submit a second swap just because the destination balance has not changed. If the source transaction succeeded, a duplicate can create a second transfer while the first is still processing.

What should you do if the destination funds are missing?

Step four is to inspect the destination transaction, if the provider supplies a hash. Open it in the destination chain’s explorer and check its receipt, token contract, recipient address and amount. A successful transaction may deliver a different token from the one expected if the route reports a partial completion, so compare the asset address as well as its ticker.

Step five is to follow the provider’s stated recovery path. If the tracker shows a refund in progress, wait for the refund transaction and verify it on the source chain. If it reports failure without a refund, give support the source hash, route ID, both chain names and any destination hash; these identifiers let the provider trace the same transfer across its stages.

Keep the original transaction hash and avoid sharing a seed phrase or signing an unrelated transaction presented as a recovery step. The next event to watch for is a destination receipt, a confirmed refund or a provider update that identifies the remaining action.