Check each transaction hash on its own blockchain before taking action. A swap can involve a payment going in, processing between networks, and a separate payment coming out. The status in a wallet or service may describe only one of those steps.
Find which part of the swap is waiting
Start with the transaction hash for the asset you sent. A hash is the transaction’s public reference number; search it in an explorer for that asset’s blockchain. Check whether it is still waiting, has entered a block, or failed.
If it is still waiting, the source network has not confirmed the payment yet. A confirmation means the transaction has been included in a block. On Ethereum, pending transactions wait in a transaction pool until a validator includes them; Bitcoin Core describes a similar pool for unconfirmed transactions. Busy networks or a low transaction fee can extend this wait.
If the source payment is confirmed, check whether the swap has produced an outgoing transaction. These are separate events: the swap service or protocol must first detect and process the incoming payment, then send the other asset. THORChain’s developer documentation describes steps for observing the inbound payment, waiting for the required confirmations, and preparing an outbound payment.
For example, say you sent ETH and are waiting for BTC. If the ETH hash is confirmed but no BTC hash appears, the delay is after the first payment. A “pending” label alone does not tell you whether the ETH is still waiting on Ethereum or whether the swap is being processed.
Give the network time before retrying
Cross-chain timing depends on both networks and the swap’s processing rules. The source chain needs to confirm the payment; the swap must then be processed; and the destination chain needs to confirm the outgoing transfer. One slow or busy network can hold up the full result.
When you check the source hash, note its status, amount, destination address, and any memo or reference attached to it. A memo is a short instruction that can help identify what the payment is for. These details help distinguish a delayed payment from one sent to the wrong address or with missing instructions.
Route choice can affect which networks and processing rules apply, so how thor swap chooses a route is relevant when you are checking where a delay may occur. A cross-chain swap service can handle the route and asset exchange in one flow, while the networks still confirm their own transactions. In a thor swap, check the source and destination hashes separately when both are available.
Do not send the same amount again just because the first attempt looks slow. If the original payment is confirmed, a second payment may create another swap. If it is still waiting, some wallets allow a fee increase or replacement transaction, but the safe method depends on the chain and wallet. Check the wallet’s guidance before replacing it.
Act on a confirmed failure or missing result
If the source transaction failed, the swap usually cannot proceed from that payment. Check your wallet balance and transaction details before trying again. If the source payment succeeded but the swap failed, a refund may be sent back to the source chain; it is a new transaction and can take time and network fees to confirm.
For a refund, verify the destination address on the source chain and compare the returned amount with the original. A refund can be smaller because the return transfer may use a network fee. If the source payment is confirmed but neither the destination asset nor a refund appears, keep both hashes and the transaction details together when seeking help through the service you used.
My rule is to retry only after I know whether the first payment failed, remains unconfirmed, or reached the swap stage. Before acting, ask yourself: Do I know which transaction is waiting, and could a retry send my funds twice?