Once you have sent your crypto, the wait begins. A swap is not one step: your transfer must be confirmed on its own network, processed by the swap service, and then sent out as a second transfer on the receiving network. Knowing where your swap sits in that chain — and which identifier to check at each stage — saves you from guessing whether something went wrong.
Two identifiers, two different jobs
Do not mix up the two identifiers you will see. The first is the service's order or transaction ID: the reference the swap service assigns to your order in its own system. Changelly's FAQ explains that this ID is not the same as the blockchain transaction ID, and it is the reference to quote if you contact that service's support. Changelly transactions FAQ (https://changelly.com/faq/changelly/transactions)
The second is the blockchain transaction ID, also called a transaction hash or TxID. This is the public record of one transfer on one blockchain. You can look it up yourself on a block explorer for that network, without asking anyone. Keep both identifiers saved until the swap is fully complete — a screenshot of the order page plus the TxID from your sending wallet is enough.
The steps a swap goes through
A typical swap moves through several stages, and each one takes time. Ledger's support guide describes the same chain: confirmation of the send transaction on the blockchain network, confirmation and processing of the received crypto by the swap provider, confirmation and processing of the sent crypto by the provider, and confirmation of the receive transaction on the blockchain network. Ledger support (https://support.ledger.com/article/4404381458065-zd)
That is why a swap can look quiet for a while even when nothing is wrong. The sending transfer may still be waiting for network confirmations, or the service may still be processing a transfer that has already confirmed. Network congestion on either network can stretch any stage, and the required number of confirmations varies by asset and by service — there is no single number that applies to every swap.
How to read a block explorer page
Open the block explorer for the network you sent from, not the network you are receiving on. Paste the TxID from your sending wallet into the explorer's search bar. On the transaction page, check four things: the status (pending, confirmed, or failed), the number of confirmations, the recipient address, and the amount.
The recipient address check matters most. It must match the deposit address shown on your swap order, character for character. If it does not, the funds went somewhere else, and that is a different problem from a slow swap. If the status is confirmed and the address matches, your side of the swap is on the chain — the remaining wait is processing and the second transfer.
Why a swap can look stuck
Pending is usually normal, not a failure. A transfer stays pending while it waits for network confirmations, and a low network fee or a busy network can keep it there longer. If the explorer shows no result at all for your TxID, the transfer may not have been broadcast yet — wait a few minutes and search again before assuming it failed.
Two other causes are worth checking early. If you sent on the wrong network, the receiving service may never see the transfer on the network it expected, even though the explorer shows it as confirmed elsewhere. If the asset needs a memo, tag, or extra ID, a transfer without it may arrive at the service but cannot be matched to your order. Both are covered in the pre-send review in the crypto swap checklist (https://moin.cash/en/resources/blog/crypto-swap-checklist) — checking them before you send is far easier than fixing them afterwards.
When to wait, and when to ask for help
Wait while the explorer still shows your transfer as pending, or while a confirmed transfer is still inside the service's normal processing stages. Congestion clears, confirmations accumulate, and most slow swaps resolve without any action from you.
Ask for help when the picture stops changing: the transfer is confirmed on the explorer with the correct address and amount, but the swap order shows no progress for a long time; the explorer shows no result well after you sent; or the transfer went to the wrong network or without a required memo or tag. When you ask, have the order ID, the TxID, the sending and receiving addresses, the amounts, and the networks ready. Those five details let support find your order without a long exchange of messages.
One rule holds for every message you send while asking for help: never share your wallet seed phrase, private key, or wallet password with anyone, including someone who claims to be support. A genuine support team can find your order from the identifiers above; it never needs your keys. If someone asks for them, stop the conversation — that is the impersonation pattern described in the support-message checks (https://moin.cash/en/resources/blog/crypto-support-impersonation-checks).
This article is general educational information. It explains how swap tracking works; it does not recommend a particular asset, service, or transaction, and it does not promise the outcome or timing of any swap.