How to Read the Mempool to See Why Your Withdrawal Is Stuck

26 September 2026

The mempool is the waiting room for unconfirmed cryptocurrency transactions. If your exchange withdrawal is stuck, reading the mempool can tell you whether the problem is low fees, network congestion, or a transaction that hasn't been broadcast at all. To find out, you look up the transaction ID (TXID) on a block explorer and check its mempool status, fee rate, and confirmation history.

What the mempool actually shows

When an exchange sends your withdrawal, it broadcasts a transaction to the network. That transaction sits in the mempool - a temporary pool of unconfirmed transactions held by nodes - until a miner includes it in a block. Each mempool has a fee threshold: transactions offering too low a fee per byte (or per virtual byte, for SegWit coins) may never be picked up if the network is busy. The mempool also discards transactions that are stale or double-spent.

A block explorer's mempool view for a specific TXID typically reports three things: - Status: "Unconfirmed" or "In Mempool" means the transaction is waiting. "Not Found" usually means the transaction was never broadcast, or it was dropped after being in the mempool too long. - Fee rate (sat/vB or sat/byte): The amount you (or the exchange) paid per unit of data. Compare this to the current recommended fee for the next block. - Time in mempool: Shows how long it has been waiting. Most mempools expire transactions after 2 - 14 days, depending on the coin.

Step-by-Step: how to check

1. Get the TXID from the exchange. Open your withdrawal history on the exchange. Look for a transaction hash (TXID) or a link to a block explorer. If the exchange has not provided a TXID, the withdrawal has not been broadcast - the problem is on the exchange side, not the mempool.

2. Open a block explorer for the correct blockchain. For Bitcoin, use a site like mempool.space, blockchain.com, or blockstream.info. For Ethereum, use Etherscan. For other coins, find the coin's official block explorer. Paste the TXID into the search bar.

3. Read the transaction details. On the transaction page, look for:

4. Confirmation count: 0 means unconfirmed.
5. Fee: Shown in the native coin (e.g., BTC, ETH). The block explorer will often display the fee rate (sat/vB or gwei).

6. Inputs and outputs: Check that the destination address matches your withdrawal address. If it doesn't, contact the exchange immediately.

7. Compare the fee rate to the mempool's current recommendations. On a mempool-focused explorer like mempool.space, the front page shows a fee chart with color-coded zones:

8. High fee zone (usually red or orange): Transactions paying this rate are likely to be confirmed in the next 1 - 2 blocks.
9. Medium fee zone (yellow): Confirmation within 6 - 12 blocks.

10. Low fee zone (green or gray): Confirmation may take hours or never happen during congestion. If your transaction's fee rate is in the low zone, it will likely stay stuck until the mempool clears or the exchange bumps the fee.

11. Look for replacement signals. Some block explorers show whether the transaction is replaceable (RBF-enabled). If it is, you (or the exchange) can increase the fee to speed it up. If no RBF flag is present, the transaction cannot be replaced unless it is double-spent.

What the mempool won't tell you

The mempool cannot show: - Whether the exchange has actually broadcast the transaction. No TXID means the withdrawal is still pending on the exchange's internal system. - Why the exchange delayed the broadcast. That could be a KYC check, a risk review, or a system error. The mempool only sees what has been sent. - Whether the exchange will bump the fee. Some exchanges automatically replace stuck transactions with higher fees; others do not. The mempool shows only the current transaction's fee.

Common scenarios and what they mean

Scenario A: TXID exists, fee rate is low, mempool is congested. Your transaction is competing with thousands of others. The exchange used a default fee that was too low for current conditions. Your options: wait for the mempool to clear (hours to days), or contact the exchange to ask if they support fee bumping. If they do, they may increase the fee on your behalf.

Scenario B: TXID exists, fee rate is reasonable, but still unconfirmed for hours. This can happen if the transaction was broadcast during a temporary spike that has since subsided. Often it confirms within a few blocks. If it remains stuck for more than 24 hours, the exchange's node may have dropped it - contact support and ask them to rebroadcast.

Scenario C: TXID shows "Not Found" or "Error." The transaction was never broadcast, or it was dropped and the exchange has not resent it. This is an exchange-side issue. Check your withdrawal status on the exchange platform; you may need to cancel and re-submit the withdrawal.

Scenario D: TXID shows confirmed on the block explorer, but the exchange still shows "pending." The blockchain has recorded the transaction, but the exchange's internal system has not updated. This is usually a sync delay. Wait 30 - 60 minutes. If it persists, contact exchange support and provide the TXID.

When the Mempool Is Not the Problem

If you find that your transaction has a normal fee rate, the mempool is not congested, and it still won't confirm, the issue may be: - Double-spend attempt: Someone tried to send a conflicting transaction. This is rare from exchanges but possible. - Node issues: The exchange's node may be out of sync or rejecting the transaction for non-fee reasons (e.g., a non-standard input). - Consensus rules: Some coins have features like "mempool full of dust" or "minimum relay fee" that can block low-value outputs.

In these cases, the mempool data will show the transaction sitting unconfirmed with no obvious cause. The only fix is to contact the exchange and ask them to rebroadcast or replace the transaction.

Practical Takeaway

Reading the mempool gives you one clear answer: whether your stuck withdrawal is a network fee problem or an exchange problem. If the fee is too low, you know to wait or ask for a bump. If the TXID is missing, you know to chase the exchange. Do not attempt to manually replace a transaction from an exchange - you could lose the funds. Let the exchange handle it, but use the mempool data to give them the correct details when you contact support.

Back to withdrawals