Level 1 · Start hereThe village#061

How long does a Bitcoin transaction take? Ten minutes on average, rarely exactly

A bitcoin payment reaches the network in seconds, then waits until a miner puts it in a block. Blocks come every ten minutes on average but at random, and payments with a low fee can wait in the queue for hours. Most receivers also wait for a few more blocks on top.

Anna pays Grandma Rosa for a jar of plum jam. Rosa looks at her phone. It says "pending". She looks again five minutes later. Still pending. "Did it go or didn't it?"

It went. Anna's note reached every house in the village within seconds. But a note isn't in the notebook until a scribe writes it onto a page, and pages close about every ten minutes. Not exactly every ten. Sometimes two in a row, sometimes none for half an hour.

And while the notes wait, they sit in a pile on the scribe's table. The scribe picks the ones with the best tips first. That's the whole answer: how long a payment takes depends on luck and on what you paid.

What it is

A bitcoin payment goes through three stages. First, your wallet sends it to the network, which takes seconds. Second, it waits in the mempool, the waiting room of unconfirmed transactions that every node keeps. Third, a miner puts it in a block: one confirmation. Each later block adds another.

Bitcoin's software aims for one block every 10 * 60 seconds and readjusts the mining difficulty every two weeks' worth of blocks to keep that average (Bitcoin Core). Average is the important word.

How it works: one evening of real blocks

Here are the 15 blocks mined on 18 November 2026 between 19:43:38 and 21:05:12 UTC, blocks 976,471 to 976,485 (mempool.space). "Why blockchains are slow on purpose" counted what was on these pages. Here we time them.

  1. The fastest gap. Block 976,482 is stamped 20:54:57. Block 976,483 is stamped 20:55:03. Six seconds.
  2. The slowest gap. Block 976,477 is stamped 20:04:09. Block 976,478 arrived at 20:37:49. Thirty-three minutes and forty seconds with no new page.
  3. The oddity. Block 976,477 carries a timestamp two minutes earlier than block 976,476 before it. Timestamps come from miners' clocks and only need to be roughly right. The order of the chain is set by the links between blocks, not the clock.
  4. The average. 14 gaps in 81 minutes and 34 seconds: about 5.8 minutes per block that evening. Fast, by chance.
  5. The long run. From block 840,000 on 20 April 2024 at 00:09:27 UTC (mempool.space) to block 976,485, the average was 9.95 minutes. Close to target.

Now look at what the long gap did. The block after it, 976,478, had a median fee rate of about 5 satoshis per virtual byte, the highest of the evening. Half an hour of payments had piled up, and the best tips went first.

The waiting room

That same evening, mempool.space showed 65,816 transactions waiting, with a total size of about 30.6 million virtual bytes (mempool.space). A block can hold at most 1 million virtual bytes: the weight limit of 4,000,000 divided by four (BIP 141). So the queue was about 30 blocks deep, five hours of pages if nobody else sent anything.

Nobody waits in line order, though. Miners pick by fee rate. mempool.space suggested 4 satoshis per virtual byte to get into the next block (mempool.space). More than half of the waiting room, about 16.3 million virtual bytes, offered around 0.12. Those payments weren't lost. They were at the back, waiting for a quiet hour.

Why it matters

  • "Sent" isn't "settled". A payment in the waiting room can still be replaced or dropped. Only a block makes it part of the record.
  • Speed is bought, not promised. A competitive fee gets you into the next block, whenever that comes. A low fee gets you a place in the queue.
  • Receivers set their own wait. The white paper shows the risk of a payment being reversed falling with each block on top (Nakamoto, 2008). That's why exchanges often wait for several confirmations. "Why you can't change the past on a blockchain" has the numbers.
  • Small, fast payments live elsewhere. Systems such as the Lightning Network move payments off the main chain for speed. That's a separate article.

Where people get it wrong

  • "Every payment takes ten minutes." Ten minutes is the average gap between blocks. We saw six seconds and almost 34 minutes on one evening.
  • "Pending means it failed." It means it's waiting. Check the fee rate against what's being confirmed.
  • "A bigger amount takes longer." The amount doesn't matter. The fee per virtual byte does.
  • "One confirmation and it's final." One block is a start. The more blocks on top, the harder it is to undo.

The sting: look at the queue before you send

Before you send, open a block explorer and look at two numbers: how full the waiting room is, and what fee rate the next block needs. If you're not in a hurry, pay less and wait. If you are, pay for the next block and accept the price.

And if someone says your payment "didn't arrive, send it again", look it up yourself. A payment that's pending is still coming. The stranger at the gate is hoping you'll pay twice.

Frequently asked questions

How long does a Bitcoin transaction take?

It reaches the network in seconds. The first confirmation comes when a miner includes it in a block, on average about ten minutes later if the fee is competitive. Blocks arrive at random, so it can be seconds or more than half an hour.

Why is my Bitcoin transaction pending?

Because it's waiting in the mempool for a miner to include it in a block. Miners choose the transactions with the highest fee per virtual byte first, so a low-fee payment can wait hours when the network is busy.

How many confirmations do I need?

There's no single rule. Each new block makes a payment harder to reverse, so receivers choose how many to wait for. Exchanges often require several, and more for large amounts.

Why don't Bitcoin blocks come exactly every ten minutes?

Finding a block is a matter of chance, like rolling dice until a rare number comes up. The software adjusts the difficulty every 2,016 blocks so that the average stays close to ten minutes, but individual gaps vary widely.

Can I speed up a stuck Bitcoin transaction?

Some wallets let you replace an unconfirmed transaction with one that pays a higher fee. Otherwise, you wait until the network is quieter and miners reach your fee rate. Nobody can push it through for you.

Sources

  1. Bitcoin Core source code, src/kernel/chainparams.cpp (nPowTargetSpacing, nPowTargetTimespan)
  2. mempool.space API, blocks 976,471 to 976,485 (18 November 2026)
  3. mempool.space API, Bitcoin block 840,000 (20 April 2024)
  4. mempool.space API, mempool summary (read on the evening of 18 November 2026)
  5. mempool.space API, recommended fees (read on the evening of 18 November 2026)
  6. BIP 141, Segregated Witness (block weight and virtual size)
  7. Satoshi Nakamoto, Bitcoin: A peer-to-peer electronic cash system (2008)

Read next.