What to do when a swap completes on the blockchain but the exchange shows nothing

05 September 2026

First, do not resend the funds. Wait. The most common cause is that the exchange simply has not processed the incoming transaction yet, and resending will either duplicate your loss or create a second stuck transaction. Then check the block explorer for the transaction ID you were given.

A swap that shows as "complete" on-chain means the network accepted your transaction and included it in a block. The exchange, however, runs its own bookkeeping. It must see that block, match the incoming address and amount to your open order, and then credit your account. That process is not instantaneous. Public blockchains confirm transactions in seconds or minutes; exchange internal ledgers can lag by minutes, hours, or occasionally longer during high traffic.

Start by verifying the transaction details. Open the block explorer and look at the exact output. Confirm the receiving address matches the one the exchange displayed for your swap. Confirm the amount matches, minus any network fee. If both match, the funds are at the address the exchange controls. They are not lost. They are waiting for the exchange's internal system to notice them.

The second check is the block confirmation count. Some exchanges require a certain number of confirmations before they credit a deposit. This is a deliberate safety measure against chain reorganisations. If your transaction has only one or two confirmations and the exchange policy requires, say, thirty, that explains the silence. Look up the exchange's stated confirmation requirement for that specific asset. The number varies by coin and by exchange policy. There is no universal figure.

If the confirmations exceed the requirement and the address matches exactly, then the issue is internal to the exchange. You cannot fix that from the blockchain. You must contact support. Do so with the transaction ID, the receiving address, the exact amount, and the time you sent it. Be prepared for a delay. Support queues are often slow. Do not open multiple tickets; that usually resets your place in line.

There is a specific mistake that causes this exact symptom, and it is worth checking before you contact anyone. Did you send the correct asset to the correct network? If you sent a token on one chain to an address that the exchange only monitors on another chain, the transaction will complete on the blockchain you used, but the exchange will never see it. The receiving address will be valid on the chain you used, but the exchange's wallet software is not watching that chain for that asset. This is not the same as sending to a wrong address. It is sending to the right address on the wrong network. In that case, the funds are not recoverable by the exchange's normal process. You will need to explain the network mismatch to support, and recovery, if possible, is a manual and slow operation.

Another possibility is that you sent to an address that was a deposit address for a previous swap and has since been retired. Some exchanges rotate deposit addresses. A completed transaction to an old address may sit uncredited indefinitely. Support can usually recover it, but again, this is manual.

Do not trust any third party who offers to "push" your transaction or "accelerate" it for a fee. That is not how this works. The transaction is already in a block. Nothing can speed up the exchange's internal processing. Anyone claiming otherwise is running a scam.

If you have verified the address, the amount, the network, and the confirmations, and the exchange still shows nothing after a reasonable waiting period - typically several hours for most assets, longer for unusual ones - then the only productive action is a support ticket. Keep your records. Screenshot the block explorer page. Screenshot the exchange's deposit screen showing the address you used. Write a clear, factual message.

For future swaps, this is exactly why the hub page on swapping crypto safely exists. Read it before your next transfer. The checks it describes - confirming the deposit address, the network, and the confirmation policy - are the same checks that would have prevented this situation in the first place. And if you are unsure about a new exchange or a new asset, the sibling page on testing a deposit address with a tiny amount before sending the full swap is the right next step. A small test transaction costs a little time and a little fee. It can save you a full swap's worth of anxiety.

In short: verify, wait, then contact support. Do not resend. Do not panic. The blockchain is a public record. The transaction happened. The question is only whether the exchange has caught up, and that is a question for their ledger, not for the chain.

Back to perpetuals