How to tell if a stuck swap is a blockchain delay or an exchange problem

05 September 2026

The first thing to check is whether the outgoing transaction has confirmed on the blockchain. If it has, the delay is on the exchange side; if it has not, the delay is a blockchain issue.

This distinction matters because the two causes require completely different responses. A blockchain delay usually resolves itself; an exchange problem may need you to contact support or wait for a manual fix.

Blockchain delays: what to look for

Open your wallet or a block explorer and find the transaction ID for the swap you sent. Look at the number of confirmations. A transaction that has zero confirmations is still in the mempool - it has been broadcast but not yet included in a block. This can happen when:

• The network is congested. Bitcoin, Ethereum, or Solana can all experience periods where many users are sending transactions at once.
• You set a low fee. Most wallets let you choose a fee tier; a low fee means miners or validators prioritize other transactions first.
• The transaction is stuck or replaced-by-fee (RBF) is possible. Some wallets allow you to bump the fee to speed things up.

If the transaction has zero confirmations and the time since you sent it exceeds typical block times (roughly 10 minutes for Bitcoin, 15 seconds for Solana, 12 seconds for Ethereum), the delay is likely blockchain-related. Wait. Most stuck transactions confirm within a few hours, sometimes longer if the network is very busy.

Exchange problems: what to look for

If the transaction has one or more confirmations on the blockchain but the exchange site still shows "pending" or "not received," the problem is on their side. Common signs:

• The exchange's own transaction history shows no incoming transaction matching your hash.
• The site displays a generic "processing" status for longer than the exchange's stated typical time (often listed in their FAQ).
• You received an email or on-site message saying "manual review required" or "funds received, awaiting credit."

An exchange delay can stem from their internal ledger not updating, a node issue on their end, or a security hold. It is not a blockchain issue.

What to do next

For a blockchain delay: Do nothing for at least one hour. If the transaction remains unconfirmed after several hours, check whether your wallet supports RBF or a "cancel" option. If it does, you can replace the transaction with a higher fee. If it does not, the transaction will eventually either confirm or drop from the mempool (usually after 24-72 hours). Do not send the same funds again - double-spending can cause both transactions to fail or one to confirm and the other to be lost.

For an exchange problem: First, verify the destination address on the exchange. Did you copy it correctly? Does it match the address shown in your exchange account? If yes, the exchange has your funds. Contact their support with the transaction ID, the sending address, and the exact time of the swap. Do not expect an instant response; exchanges process these manually. If the exchange has a status page or social media account, check for known issues.

When to involve the hub page

If you have confirmed the transaction on the blockchain, verified the address, and the exchange still shows nothing after 24 hours, you have moved beyond simple troubleshooting. At that point, the next logical step is to read Swapping crypto safely - the hub page this set belongs to - which covers the broader checks you should have made before sending funds, including how to assess an exchange's reputation and what recourse you actually have. That page will help you decide whether the problem is worth pursuing further or whether the funds are effectively lost.

Back to card purchases