Four checks to make when a cross-chain swap is delayed

A delayed cross-chain swap can be held up at the source, during the route or on the destination chain. Check each stage before retrying: a second swap could spend more funds while the first one is still moving.

Did the source transaction confirm?

Start with the transaction on the chain where you sent the funds. A transaction hash is a public record you can look up on that chain’s block explorer, a site that shows transaction status. Check whether it is pending, confirmed or failed, and whether the amount and destination address match your swap.

A pending transaction has not finished on the source chain, so the cross-chain process may not have started. If it failed, look for a reason in the transaction details before trying again. For a route-level comparison, the fuller guide to thor swap explains how route choices can affect a cross-chain trade.

Has the swap service picked up the transfer?

If the source transaction is confirmed, check the swap service’s status page or interface for the same transaction. Cross-chain swaps often rely on a service or network of operators to observe the source payment and arrange the next step. That handoff can take time, and a confirmed source transaction does not by itself prove the destination transfer is complete.

Compare the transaction hash, source chain, destination chain and amount shown in the status view. If the service reports a problem, use its official support channel and share the hash. Never share a wallet recovery phrase or private key.

Has the destination transaction arrived?

Look up the destination address on the destination chain’s block explorer. Check for an incoming transaction and confirm the token and amount. Some wallets hide tokens until they are added to the display, so an empty-looking balance is not proof that funds are missing.

If there is no destination transaction yet, the transfer may still be waiting for the route to complete. If one appears, check whether it succeeded and whether the token is the one you expected. A failed destination transaction and a pending one call for different next steps.

What should you check before taking action?

Match the records across the source, swap service and destination. Keep the details together:

• Source transaction hash and status
• Destination address and chain
• Expected token and amount
• Any route status or error message

Use the service’s stated recovery steps if the route has failed or stopped. Avoid starting another swap until you know whether the first is complete or recoverable. The next thing to watch is a destination transaction or a clear status update from the service; either tells you more than the source confirmation alone.