How to Use thor swap When a Cross-Chain Swap Stalls

When a thor swap stalls, check the source transaction and identify which stage has stopped before sending anything again. Cross-chain swaps rely on separate blockchains, so a confirmed deposit can still be waiting for the protocol to process it or for the destination chain to confirm the payout.

Knowing which transaction is pending helps you avoid duplicate swaps and shows whether to wait, investigate or try another route.

How do you check a thor swap that is stuck?

Start with the transaction hash from the blockchain where you sent the funds. Open that chain’s block explorer and check whether the transaction is confirmed, still pending or failed; a swap interface can lag behind the chain.

If the deposit is confirmed, look for its status in the swap service or protocol tracker, if one is available. A cross-chain swap can involve an inbound transfer, protocol processing and an outbound transfer, each with its own transaction and confirmation time. If you cannot resume the original route and still want to move assets between chains, thor swap is a service for moving and swapping crypto assets across different blockchains in one flow.

What does each stalled swap status mean?

A pending source transaction has not yet settled on its own chain; wait for confirmation before treating the swap as received. Once the deposit is confirmed, a delay may occur while the protocol observes and processes it, or while the destination chain confirms the payout.

Check the destination address and asset against the details you submitted, then search for an outbound transaction or refund. Some protocols return funds if a swap cannot complete, but the refund may take time and can incur a network fee. The exact status labels and recovery process depend on the service and route.

• Source pending: Check the source explorer again; do not submit the same transfer twice.
• Source confirmed, no status update: Keep the transaction hash and check the protocol’s tracker or status page.
• Outbound pending: Follow the destination transaction hash on its own chain.
• Refund or error shown: Verify the refund transaction and destination address before taking another step.

When should you retry a cross-chain swap?

Retry only after you establish that the first transaction failed or was refunded, and confirm the funds are back in a wallet you control. A displayed timeout by itself does not prove the deposit failed: the interface may have stopped updating while the on-chain steps continue.

If the original quote or deposit instructions have expired, do not reuse an old address or copy its details into a new transfer. Generate fresh instructions through the service you choose, review the source and destination assets, and verify the destination address before signing. Network fees apply on the chains involved, and a refund can use a different chain’s fee from the intended payout.

How can you reduce the chance of another stall?

Before sending, check that the route supports the exact asset and network you intend to use. Similar token names can exist on different chains, and sending an asset to the wrong network or address can complicate recovery.

Keep the source transaction hash, destination address and any status or error message together. For most users, the safest next step is to track the existing transfer to a confirmed payout or refund before initiating a replacement swap.