A Cross-Chain Swap Is Pending During a Network Halt: What to Do

If a network in your cross-chain swap has halted, wait for it to resume and check the transaction on that chain before trying again. A halt can pause one part of a swap even when the other network is working normally.

Keep three points in mind:

• A submitted deposit may be confirmed while the swap’s next step is waiting.
• Check the transaction on the network where it was sent; an app’s pending label alone is not proof of failure.
• Do not send the same amount again until you know what happened to the first attempt.

What does a network halt do to a pending swap?

It stops or slows the chain’s ability to confirm transactions, so the swap cannot safely move through every step. A cross-chain swap connects separate networks; it does not make them share one transaction or one clock.

For example, your Bitcoin deposit might confirm, then the service may need to wait before it can complete the next action on Ethereum. If Ethereum has stopped producing blocks, that action cannot be confirmed there until the network resumes. The swap may stay pending during the wait.

That is why a thor swap service is useful for the task: it handles the cross-chain movement in one flow. If a network halts midway, check the deposit’s transaction record and save its transaction ID before deciding what to do next.

How can I tell where the swap is stuck?

Find the deposit transaction ID—the public reference for a transaction—and look it up on the explorer for the network you used. Check whether it is unconfirmed, confirmed, failed, or absent; those states point to different next steps.

Say you are swapping BTC for ETH. If the Bitcoin deposit has confirmations but the destination chain is halted, your input may be received while the output waits. If the Bitcoin transaction itself is still unconfirmed, the delay is at the source, and the swap’s later steps may not have started.

A halt can also be confused with a slow wallet or explorer. Compare the transaction on a second reputable explorer, and check the network’s official status channel if blocks appear to have stopped. Ethereum.org explains that Ethereum proof-of-stake finality depends on validators agreeing on checkpoints; Solana’s documentation distinguishes recent, confirmed, and finalized states. A transaction appearing briefly is not always the same as one being settled.

What should I do while it is pending?

Wait if the deposit is confirmed and the affected network has stopped producing blocks. A swap service may wait for the network to recover, then continue, or follow its own refund process; the exact outcome depends on the service and where the halt occurred.

Do not repeat the deposit just because the app still says pending. The first transaction could complete after the network resumes, leaving you with two deposits. Also avoid sending a separate “replacement” payment unless you have confirmed the original failed and understand how the service handles recovery.

Once the network is moving again, check the original transaction and the swap’s status. If the deposit is confirmed but the swap has not progressed, contact the service through its official support channel with the transaction ID and destination details. For a thor swap, that record helps distinguish a delayed network step from a deposit that never arrived.

Your next step is simple: verify the original transaction on its source chain, then wait for the halted network to resume before taking further action.