Bitcoin fees and the mempool: why a cheap transfer waits for hours

Key takeaways
- A Bitcoin fee is charged per byte of data, not per amount sent, so 0.002 BTC and 2 BTC can cost exactly the same to move.
- A transaction that pays too little is not lost: it waits in the mempool until fees fall, the network forgets it, or you replace it.
- We pay out after 2 confirmations, and because blocks arrive at random, a wait of 40 minutes is unusual but not a fault.
You paid a Bitcoin fee of a couple of dollars, the wallet says sent, and three hours later the transaction is still unconfirmed. Nothing is broken: your transfer is standing in a queue sorted by price, and yours is near the back. This piece explains how that queue works, how to jump it with a replacement or a child transaction, and why we begin a payout after two confirmations when other services insist on six.
The fee is priced by size, not by value
A Bitcoin transaction is a small data file, and miners sell space in a block, which holds about one million virtual bytes. A plain payment with one input and two outputs, yours and your change, weighs around 141 virtual bytes. You offer a rate in satoshis per virtual byte. At 15 satoshis per byte that is 2,115 satoshis, or about $1.34 with Bitcoin at $63,480. At 60 satoshis per byte it is 8,460 satoshis, about $5.37. That spread is the whole reason our guide quotes Bitcoin fees as $1 to $6. A wallet that gathers many small inputs makes a heavier file and pays more, which is why a tidy wallet with a few large inputs sends cheaper than one fed by fifty small deposits. Fee estimates in a wallet are guesses about the next hour. A slider offering a target of one block, six blocks or a day is only choosing a different line on the same queue. If the transfer is not urgent, the slow setting often costs far less than the fast one, and it is the low figure that fits the $1 end of the range. The price you pay is patience, and patience is only free if nobody is waiting on the coins.
The mempool is a queue sorted by price
Once you broadcast, every node that accepts your transaction keeps it in its own waiting area, the mempool. Miners build the next block by taking the highest rates first until the space runs out. When demand is quiet, even 2 satoshis per byte clears in the next block. When demand spikes, the rate needed for the very next block can triple in an hour, and your cheap transfer slides to the back. Nodes do not hold the queue forever: the default memory cap is about 300 MB, the cheapest entries are dropped first when it fills, and an unconfirmed transaction is forgotten after 14 days. A public mempool page shows the current rates for the next block, the third block and the sixth. Compare your own rate against those lines before you decide to wait. Rushes come in bursts, often when the market moves sharply, and a mempool page shows them building before you send. A quiet weekend can cost a fraction of a weekday price for the same transfer, because the queue is shorter and miners have room to take everything offered. You cannot predict a rush, but you can look at the page for ten seconds and choose the speed that matches your hurry.
The order matters more than it looks. Doing these two things in the wrong sequence is the difference between a locked rate and whatever the market gives you twenty minutes later.
Getting unstuck: replacement and a child that pays
There are two real fixes. The first is replace-by-fee. If your wallet marked the transaction replaceable, which most modern ones do by default, you can resend the same coins with a higher fee and the old version is discarded. The new fee must beat the old one in absolute terms, not only in rate, and exchange withdrawals usually do not offer the button at all. The second is a child transaction. Whoever controls an output of the stuck transaction spends it in a new transaction with a generous fee, and miners treat the pair as one package because they cannot take the child without the parent. That works for the receiver or for you through the change output. If your rate is within a few satoshis of the next-block line, waiting is cheaper than either. One warning for the receiving side. A replaceable transaction can be swapped for a version that pays the coins somewhere else, which is the reason nobody should treat zero confirmations as money. If you want to speed up a payment to us, write to support with the transaction ID before you do anything,.
| Route | Cost | Settlement | Who you trust |
|---|---|---|---|
| Bank card | shown in the order | depends on the issuing bank | Exchanger and issuing bank |
| Bank transfer | shown in the order | follows banking days | Two banks and a compliance officer |
| P2P on an exchange | set by the seller | minutes to hours | A stranger and an escrow |
Why two confirmations for us, six elsewhere
The figure of six is a habit from merchants selling goods that cannot be recalled, and it is conservative on purpose. A chain reorganisation of one block happens occasionally, two blocks deep almost never. We start a payout after two because for most orders the extra hour is not worth it to you, and we accept the small remaining risk on our side, since a bank transfer we send cannot be pulled back. That is a trade-off, not a free lunch: two is faster and slightly less safe than six, and the exposure sits with us rather than with you. It is also why the Bitcoin reserve of 6.42 BTC and the order limits exist. They cap what a single bad block can cost. There is a second layer of protection that has nothing to do with confirmations. Each order gets its own receiving address, so we always know which transaction belongs to which order, and a payment that arrives short or late is matched by hand rather than guessed. The two confirmations are the floor for starting, and a person looks at the rest.
Ten minutes on average, forty on a bad run
Bitcoin finds a block every ten minutes on average, but the finding is random, so the gaps vary widely. The chance that one particular block takes longer than forty minutes is about 1.8 percent. For two blocks in a row the chance that both together take more than forty minutes is about 9 percent, roughly one run in eleven. These are properties of the lottery, not of your transfer. A slow block stretches it, and nothing on your order is wrong when that happens. What does matter is that a transaction with the right fee and zero confirmations is simply waiting its turn, and the counter will move without any action from you. A practical way to use all this: if you send Bitcoin and plan to leave your computer, set the fee by the rate that clears the next block, not by the cheapest line. The saving from the low setting is usually a dollar or two, and the cost of a stuck transfer is your afternoon. Before writing to support, open the transaction in an explorer and read its status line, because the answer to most questions is already printed there.