Bitcoin transaction confirmation — that's the phrase behind every anxious support ticket at a crypto exchange. "Sent 20 minutes ago, still nothing." Bitcoin transfers aren't instant, and those 10–30 minutes of waiting hide a whole mechanism most people never think about. Once you understand how it works, you'll know exactly when to credit a payment — and when there's actually something to worry about.
The Mempool: The Queue Your Client Never Sees
When someone hits "Send" in a Bitcoin wallet, the transaction doesn't go straight to the blockchain — it lands first in the mempool (short for memory pool). Think of it as a global waiting room: thousands of transactions that have been broadcast to the network but haven't made it into a block yet.
Picture a post office where the couriers (miners) get to pick which parcels to take. They don't have to go in order — they take whatever pays the most. So your transaction might wait a minute, or it might sit there for several hours.
The size of the mempool is a live gauge of network load. On a quiet day, a few hundred transactions. During peak activity, tens of thousands. That's why Bitcoin feels fast some days and agonizingly slow on others — it all depends on how crowded the queue is.
How Miners Pick Transactions
A miner builds a block by selecting transactions from the mempool to maximize fee revenue. The key metric is fee rate: satoshis per virtual byte (sat/vByte). The higher the rate, the sooner a transaction gets included.
SegWit transactions (bc1... addresses) take up less virtual space than older legacy formats. That's why wallets supporting SegWit can pay a lower absolute fee and still get the same priority. If your exchange still accepts legacy P2PKH addresses (starting with 1...), your clients are overpaying for the same speed.
One block holds roughly 1–4 MB of transactions in virtual bytes. A new block is found on average every 10 minutes — but that's an average, not a schedule. Sometimes three blocks arrive in 15 minutes; sometimes the next one takes 40.
What "1 Confirmation" Means and How Many an Exchange Should Wait For
One confirmation means the transaction was included in a block. Two means another block was mined on top of it, and so on. Each additional block makes rewriting that history exponentially more expensive: reversing a transaction with six confirmations is vastly harder than reversing one with a single confirmation.
In practice, most exchanges credit small amounts after 1–2 confirmations. Medium amounts: 3–6. For very large transactions, some platforms wait for 12 or more. This isn't paranoia — a double-spend attack is technically possible at 0 confirmations and theoretically feasible at 1, if the attacker controls enough hash power.
A zero-confirmation transaction is a promise, not a fact. Don't credit it automatically, especially for large amounts.
Fees, RBF, and Stuck Transactions
If the sender set too low a fee rate, the transaction can sit in the mempool for hours or a whole day. Sometimes the mempool clears out overnight when activity drops — and a quietly stuck transaction suddenly confirms 18 hours later. The client calls to say thanks, but neither of you knew when it would happen.
RBF (Replace-By-Fee) lets the sender replace a stuck transaction with a new one carrying a higher fee. If the original was flagged as opt-in RBF (via the nSequence flag), this swap is possible before the first confirmation. For an exchange, this is a double risk at 0 confirmations: the transaction might never confirm, or it might be replaced entirely. Don't credit RBF-flagged transactions until the first confirmation arrives.
CPFP (Child-Pays-For-Parent) works from the receiver's side. You create a new transaction that spends the incoming funds and carries a high fee. Miners look at that "family" of transactions together. If a client sent you funds with a low fee and you want to speed things up — CPFP is your lever.
What to Do With a Stuck Bitcoin Transaction
A client writes: "Sent an hour ago, 0 confirmations." The process is straightforward.
- Ask for the TXID (transaction hash) and look it up on mempool.space — it shows the transaction's current fee rate and overall network congestion clearly.
- If the fee rate is below the current minimum for block inclusion, the transaction is just waiting its turn. Tell the client honestly: the network is busy, we're waiting.
- If the client's wallet supports RBF, they can raise the fee themselves through a "Speed up" or "Boost" option.
- If the transaction has been stuck for more than 72 hours and network load is low, there's a good chance it will drop out of the mempool and the funds will return to the sender automatically.
No need to panic, and no need to promise fixed timelines. The Bitcoin network runs on its own rules — your job is to explain them, not bend them.
Conclusion
A Bitcoin transaction isn't an instant transfer — it's a process with a queue, a bidding war for block space, and probabilistic confirmation. Understanding the mempool and miner logic means you stop guessing and start explaining the real picture to clients. Less support stress, more trust in your platform.
If you're launching or already running your own exchange, iEXExchanger provides a ready-made engine with automated transaction processing and configurable confirmation thresholds — no need to build that logic yourself.
