Bitcoin confirmation taking hours? Here is what each hour means

The question usually arrives as a number of hours. Two hours. Six hours. Eighteen hours and counting. The number matters, because each stretch of time rules things out, and by the time you reach a full day the transaction has told you almost everything about itself.

What follows is the reading at each stage, using the live measurements this site publishes every morning. On 10 October 2026, when this was written, the next block was clearing down to 0.26 sat/vB, the median rate inside it was 1.0 sat/vB, and 77.7 percent of the 79,896 waiting transactions sat in the 0.1 to 0.2 sat/vB band, about forty blocks deep. Keep those three numbers in mind. They explain every row below.

Under 30 minutes: nothing is wrong

Blocks average ten minutes apart, but they arrive at random. A twenty or thirty minute wait for the first confirmation happens most days and means nothing. Wallets that show a progress bar or an estimated time make this worse, because the estimate was only ever an average.

If your fee rate is at or above the next block rate, the only thing between you and a confirmation is a coin toss that lands roughly every ten minutes. Make a coffee.

30 minutes to 1 hour: probably a slow block, possibly a low fee

Gaps between blocks longer than half an hour happen in roughly one block in twenty. Gaps over an hour happen a few times a month. So a transaction pending for forty five minutes with a good fee rate is unlucky, not stuck.

This is also the first moment a low fee shows itself, because by now three or four blocks have usually been found and none of them took you. The way to tell the two apart is the same check used at every stage of this article:

Our free checker does both halves of that in one step and shows the two numbers side by side.

1 to 6 hours: your fee is below the clearing rate

By the time a transaction has been pending for a few hours, somewhere between twelve and thirty six blocks have gone by. At a good fee rate the odds of missing all of them are effectively zero. So a transaction pending this long is priced below what blocks are taking, and the only question is by how much.

The middle row is the one that produces most "taking hours" searches. A wallet's economy option often lands around 0.3 to 0.5 sat/vB, which is fine on a quiet Sunday night and a multi hour wait on a weekday afternoon. Nothing is broken. The transaction is simply queued behind everyone who paid more, and new transactions paying more keep arriving in front of it.

What waiting longer actually does

Waiting works only if the clearing rate drops below your rate. It does dip at quiet hours, so a transaction at 0.4 sat/vB may well confirm at three in the morning. A transaction at 0.15 sat/vB will not, because the band it sits in is forty blocks deep and refills faster than it drains. Below about 0.26 sat/vB today, the clock is not on your side.

6 to 24 hours: it will not confirm by itself

A transaction pending for most of a day has watched well over a hundred blocks go past. At this point it is almost always in the standing queue near the relay floor. Since Bitcoin Core 29.1 lowered the default minimum relay fee to 0.1 sat/vB in September 2025, that queue has been permanent: most of the mempool, every day, parked at a rate miners never need to reach.

The good news is that this transaction is in no danger. It has not failed. Your coins have not moved. And the fix is small.

Which fix depends on which side of the payment you are on.

• You sent it. Bump the fee with RBF. Your wallet re signs the same payment with a higher fee and the new version replaces the old one everywhere. Electrum, Sparrow, Bitcoin Core, BlueWallet, Trezor Suite and Ledger Live all have the button.
• You received it. Spend the incoming output with a high fee. Miners weigh parent and child together and the child pulls the parent in. This is the standard fix for a slow exchange withdrawal.
• You can do neither. An exchange sent it and you have no spendable output yet. Ask their support to bump it, wait, or in the one genuine case for a paid service, use a pool accelerator that names its pool.

Beyond 24 hours: the same situation, with a deadline

Nothing changes between day one and day thirteen except that the fix becomes more urgent. Most nodes keep an unconfirmed transaction for 336 hours, fourteen days, then discard it. Before that, a node whose mempool hits its 300 MB memory limit may evict the lowest paying transactions early. Either way, when the transaction is dropped the coins become spendable again from the sending wallet and nothing has been lost. The full timing guide covers the expiry and the seventy two hour myth that still circulates.

If you want the payment to go through rather than evaporate, bump it before then. If you would rather it evaporated, stop and let it.

Two cases where the hours mean something else

An exchange says sent but there is no transaction ID

Exchanges batch withdrawals, run internal reviews and move coins out of cold storage on their own schedule. All of that happens before anything is broadcast. If the exchange shows pending but cannot give you a sixty four character transaction ID, the Bitcoin network has not received anything yet and nothing on the network can speed it up. The exchange withdrawal guide goes through this by platform.

Your wallet says pending, every explorer says not found

Then the broadcast never happened, or the transaction was already dropped. Hours of waiting change nothing because no node is holding anything to confirm. This is the one case where rebroadcasting is the right fix: push the raw transaction back to many nodes, free, through this site or by hand. The not found guide explains how to tell this case from a simple explorer delay.

Does the amount matter?

No. Miners order transactions by fee rate per virtual byte, never by value. A ten dollar transfer and a ten million dollar transfer at the same sat/vB are interchangeable to a block template. Confirmation count thresholds at exchanges are a separate policy question, covered below, but the time to the first confirmation is pure fee rate.

Does the time of day matter?

A little, at the edge. The clearing rate drops during quiet hours and at weekends, so a transaction just under it may confirm in a lull. It does not matter at all for transactions in the floor band, which is where a transaction pending for a day almost always is. Do not plan around the lull. Plan around the fee rate.

The bottom line

Under an hour, assume a slow block and check the fee rate once. A few hours in, the fee is below the clearing rate and waiting works only at the margins. A day in, it will not confirm by itself, the coins are safe, and the fix costs about as much as a text message. Read the hours, then act on the sat/vB.