Bitcoin Latest Blocks

The newest blocks as miners find them — one every ~10 minutes on average, each carrying the 3.125 BTC subsidy plus fees.
-- loading…
Last 15 Blocks
HeightAgeIntervalTxnsFees (BTC)Size (MB)Pool
loading blocks…
Interval = time since the previous block. Fees = total transaction fees paid to that block's miner (on top of the 3.125 BTC subsidy). Ages and intervals use miner-reported timestamps — an occasional negative interval is clock skew, not a chain problem. Heights link to the full block on mempool.space.
Avg interval (last 10)
--
vs 10m 0s target
Avg fees / block
--
BTC per block, last 15
Avg txns / block
--
transactions, last 15
Avg block size
--
MB serialized, last 15

What is a block?

A block is a batch of transactions bundled under a small header that commits to the previous block's hash, a merkle root of the transactions, a timestamp and a nonce. Miners race to find a header hash below the current difficulty target; the winner appends the block to the chain and collects the 3.125 BTC subsidy plus every fee in the block. The table above shows each winner's height, timing, contents and pool as blocks arrive.

Why block intervals are random

Hashing is memoryless: every one of the network's hash attempts is an independent lottery ticket, and past effort builds no progress toward the next block. Block arrivals therefore form a Poisson process, and the gaps between them follow an exponential distribution — the expected interval is 10 minutes, but the actual intervals in the table scatter from seconds to the better part of an hour. That spread is the system working as designed.

P(no block for t minutes) = e^(−t / 10)
P(gap ≥ 45 min) = e^(−4.5) ≈ 1.1% of gaps → roughly 1–2 per day
average blocks per day = 86,400 s ÷ 600 s target = 144

From block pace to the difficulty adjustment

Individual intervals are noise, but their average over 2,016 blocks is the signal Bitcoin retargets on. If the epoch's blocks averaged faster than 10 minutes, difficulty rises proportionally at the next retarget; slower, and it falls. The "avg interval" tile above is a small live sample of that same pace.

new_difficulty = old_difficulty × (20,160 min ÷ actual_time_of_last_2,016_blocks)
e.g. epoch avg interval 9m 40s → next adjustment ≈ +3.4%

Why it matters for miners

The Fees column is the variable half of your revenue: hashprice is built from the subsidy plus the average fees per block, so a sustained change in the fee level here moves earnings per TH/s directly. Block pace is your early warning for the next retarget — consistently fast blocks mean hashrate has joined and an upward adjustment is coming. And the raw interval variance is why small pools and solo miners see lumpy payouts even when their hardware is running perfectly.

Rule of thumb: fees in calm periods are a few percent of the block reward; during congestion they can multiply. The calculator uses the live average fees per block automatically.

FAQ

Why was there just a 45-minute Bitcoin block?
Block discovery is a Poisson process: every hash is an independent lottery ticket, so the gaps between blocks follow an exponential distribution around the 10-minute average. About 1.1% of gaps run longer than 45 minutes — roughly one or two per day — and they are normal variance, not a network problem.
How many Bitcoin blocks are mined per day?
144 on average — 86,400 seconds per day divided by the 600-second block target. The actual daily count wanders with luck, and runs slightly above 144 while hashrate is growing inside a difficulty epoch.
What decides how big a Bitcoin block can be?
Consensus rules cap each block at 4 million weight units — up to about 4 MB in edge cases, typically around 1.5–2 MB serialized. Miners fill that space with the highest fee-rate transactions waiting in the mempool.
Source: mempool.space API (blocks, fees, pool tags) — cross-checked live against BasinTwo's own synced Bitcoin full node. Updated every 60s in your browser.