Cross-Chain Swap Stuck? Check These Three Transaction Stages

When a cross-chain swap stalls, check the source-chain transaction first, then the bridge status and destination wallet to find which step needs action. A swap usually involves a transaction on the starting blockchain, a wait for confirmation or message delivery, and a final transaction that releases or mints tokens on the destination chain.

How do I tell where the swap is stuck?

Find the source transaction hash in your wallet’s activity and open it in an explorer for that chain. Ethereum.org explains that a transaction can remain pending until it is included in a block, replaced by another transaction with the same nonce, or dropped; if it failed, the explorer should show that status.

If the source transaction succeeded, check the bridge or swap service’s status page using that hash. The source transaction may have completed while the message, attestation or relay is still in progress. For a clearer estimate of the costs involved, see fermi swap’s breakdown of bridge fees, gas and slippage; the total can include separate costs on both chains.

What should I do if the source transaction is pending?

Wait if the transaction is still pending and the network is busy. If your wallet offers a speed-up option, it generally resubmits the same transaction with a higher fee; Ethereum.org says a cancellation uses the same nonce to replace the pending transaction. Replacement rules vary by network and wallet, so follow its instructions and verify the new transaction hash.

Do not start a second swap while the first transaction’s status is unclear. If the original transaction later confirms, a second attempt could send funds twice. If the explorer marks it failed, check whether the swap service recorded a deposit before trying again; a failed source transaction does not by itself mean a bridge transfer is underway.

What if the source transaction succeeded but nothing arrived?

Use the original hash in the bridge’s own tracker and check whether it is waiting for confirmations, a message, or destination-chain execution. Wormhole’s documentation describes transfers where a relayer handles redemption automatically, as well as manual flows that require a separate completion transaction. Those stages can have different wait times and requirements.

Follow the service’s recovery instructions if it shows that a manual claim is available. Check that you selected the right destination network and wallet, and that the wallet has that network’s native token if a claim transaction needs gas. A transfer can be recorded on the source chain without the destination transaction having run yet.

• Pending on source: wait or use the wallet’s speed-up process.
• Failed on source: confirm the bridge did not record a successful deposit before retrying.
• Confirmed, awaiting relay: track the original hash and wait for the bridge’s next status update.
• Claim available: complete it through the original service’s official interface.

Share a transaction hash with support only through the service’s verified channel; never give anyone your seed phrase or private key. Wormhole’s documentation also notes that some transfers can only be completed by the app that initiated them, so a different bridge interface may not be able to claim the funds.

After the tracker reports completion, check the destination wallet on the correct network. If the status remains unchanged beyond the service’s stated processing window, contact its support with both chain names and the source hash; the next step is a status check from the team operating that route.