Block Time

Block time is the average time a blockchain network takes to produce a new block. It determines how often batches of transactions are added to the ledger and how quickly users receive their first confirmation. Bitcoin targets about 10 minutes per block, Litecoin about 2.5 minutes, Ethereum produces blocks in 12-second slots, and some high-throughput networks such as Solana aim for well under a second.

On proof-of-work networks, block time is a statistical average that varies from block to block, because finding a valid block depends on chance. The network keeps it near its target by adjusting mining difficulty. On many proof-of-stake networks, blocks are scheduled at fixed intervals, though some slots may be missed. Block time is related to, but different from, finality, which is the point at which a transaction can no longer be reversed, and to throughput, measured in transactions per second.

Think of a bus route. If a bus leaves every 10 minutes, a passenger arriving at the stop waits on average five minutes, and each bus carries a set number of people. If buses leave every minute, waits are shorter, but the route needs more coordination and buses might bunch up or collide at junctions.

Blocks are like those buses, carrying transactions. A short block time means your payment is picked up sooner. But if blocks come too fast for the network to share them with everyone, two "buses" may leave at once from different stops, creating confusion about which one counts. Each blockchain picks a timetable that balances speed and reliability.

On Bitcoin, the protocol adjusts mining difficulty every 2,016 blocks, roughly every two weeks. The new difficulty depends on how long the last 2,016 blocks actually took compared with the expected two weeks:

• $D_{\text{new}}$ is the new difficulty and $D_{\text{old}}$ the previous difficulty.
• $T_{\text{expected}}$ is the target time for the period, 2,016 blocks times 10 minutes, or 20,160 minutes.
• $T_{\text{actual}}$ is the time the period actually took.

Suppose new mining machines come online and the last 2,016 blocks took 18,144 minutes, an average of 9 minutes per block. The new difficulty is $D_{\text{old}} \times 20{,}160 \div 18{,}144 \approx D_{\text{old}} \times 1.111$, an increase of about 11%. With the same hashrate, blocks then return to an average of about 10 minutes. Bitcoin limits each adjustment to a factor of four in either direction. Proof-of-stake chains, by contrast, simply schedule a proposer for each slot, so block time is set directly by the protocol.

These figures are targets or typical values as of November 2026, and several networks have shortened their block times through upgrades.

Shorter block times give faster confirmations and a smoother user experience, but they have costs. Blocks need time to spread across a global network; if a new block is found before the last one has reached everyone, two competing blocks can appear, leading to stale blocks and short reorganisations. Frequent stale blocks waste work and can favour well-connected miners or validators, encouraging centralization. Shorter intervals also mean more blocks to store and verify. Longer block times are more robust but slower, which is one reason Bitcoin users wait for several confirmations for large payments. Many projects combine moderate block times with layer 2 systems such as the Lightning Network to offer fast payments.

For users, block time affects how long exchanges take to credit deposits, how fees behave and when transactions can be considered settled. On Bitcoin, the randomness of block discovery means an hour can pass without a block, even though the average is 10 minutes, which can push up fees during busy periods. Finality rules matter too: a transaction in a block may still be reversed until enough later blocks are built on it, a concept described in probabilistic finality. Merchants and exchanges set their own confirmation requirements based on the amount and the network's block height progress.

Block time also interacts with block size. Together they set the network's maximum capacity: a chain that produces 1 megabyte every 10 minutes can carry far fewer transactions than one producing several megabytes every few seconds. Raising either number increases capacity but also increases the bandwidth, storage and processing power needed to run a node, which is the core of long-running debates over how to scale blockchains without sacrificing decentralization. Developers therefore treat block time as one lever among several, alongside fee markets, compression and off-chain layers.