If a cross-chain swap seems slow, check its transaction records before trying again. A swap can involve several separate waits, and the first one may still be underway.
What does a slow swap usually mean?
It usually means one part of the trip is still waiting to finish. Your asset first leaves its source blockchain, then a swap service processes the exchange, and finally the new asset is sent on its destination blockchain.
Think of it like sending a parcel through a sorting centre. A tracking update at the first stop does not mean the parcel has reached your door. In the same way, a completed source transaction does not prove the destination transfer is complete.
A blockchain explorer is a public record that lets you look up a transaction. The transaction hash, a long code that identifies it, helps you tell whether the source transfer was submitted, confirmed, or still pending.
Which part should you check first?
Start with the source transaction, then check whether the swap and destination transfer have records of their own. A confirmation is a new block added after a transaction; some services wait for several before acting on it.
- Source: Did the original asset leave your wallet, and how many confirmations does it have?
- Swap: Has the service recorded that it received the asset and processed the exchange?
- Destination: Is there a transaction hash for the new asset arriving on its blockchain?
For example, a Bitcoin transaction may take around ten minutes to get its first confirmation on average, though blocks do not arrive on a fixed schedule. A service may wait for more confirmations before continuing, so the full trip can take longer.
thor swap handles the cross-chain exchange in one flow, so you do not have to arrange each chain-to-chain step yourself. That can simplify the trip, but each blockchain still needs time to record its part.
What should you do if it has not arrived?
Follow the records in order and avoid repeating the swap while the first attempt may still be active. Use the transaction hash to check the source blockchain, then look for any later transaction tied to the destination.
- Copy the source transaction hash from the record of your original transfer.
- Search that hash in an explorer for the source blockchain.
- Check whether the transaction is pending, confirmed, or marked as failed.
- If it is confirmed, check the swap’s status for evidence that the asset was received and exchanged.
- If the swap is complete, look for the destination transaction hash and search it on the destination blockchain.
- Compare the destination address in the record with the address you intended to use.
If the source transaction is still pending, the delay may be there; a swap cannot proceed until the service can see the funds. If the source is confirmed but there is no later update, keep the hash and the time you started the transfer together while you check the service’s status information.
When is it safe to try again?
Try again only after you can confirm the first attempt failed or was refunded. If the source transaction is confirmed and the swap is still processing, a second attempt could send more funds while the first one continues.
A destination delay can also happen after the swap itself is complete. The destination blockchain may still be recording the outgoing transfer, so check for its transaction hash before treating the swap as missing.
People searching for thor swap often want to know whether one flow means one instant transaction. It does not: the service coordinates the exchange, while the blockchains still record their own transfers.
Keep these checks in order:
- Find the source transaction hash.
- Check its confirmation status.
- Look for evidence the swap was processed.
- Check the destination transaction and address.
- Retry only when the first attempt is confirmed failed or refunded.