What Is Block Height?

Every Bitcoin block sits in a fixed position in a single, ever-growing line. Block height is the number that marks that position. It counts how many blocks came before, and because Bitcoin produces blocks at a steady average pace, that count doubles as the network's clock. When someone holds a screen up and says "this was the block," they are reading Bitcoin's own way of telling time.

This article explains what block height measures, why a simple count can act as a clock, and why that design makes Bitcoin's past so expensive to rewrite.

What block height actually counts

Block height is the number of blocks in the chain before a given block, counting from the very first one. The first block, called the genesis block, has height 0. The block after it has height 1, then 2, and so on. There are no gaps and no branches in the version everyone agrees on. Height is simply a running tally of confirmed blocks.

The genesis block is the fixed root of the whole structure. It was mined on 3 January 2009, and its coinbase data carries a newspaper headline: The Times 03/Jan/2009 Chancellor on brink of second bailout for banks. Every block since then points back, one link at a time, to that single starting point.

Because each block also carries a fingerprint of the block before it, the chain has a strict order. You cannot slot a block in between two existing ones, and you cannot renumber them. Height is not a label someone assigns. It falls out of the chain's own structure.

Why a count can tell time

A count of blocks would be useless as a clock if blocks arrived at random. Bitcoin fixes the pace. The network aims for one new block roughly every ten minutes on average, which works out to about 144 blocks per day and 6 per hour.

Nothing enforces that pace directly, because no one controls how much computing power is pointed at the network. So Bitcoin adjusts the difficulty of mining instead. Every 2016 blocks, about every two weeks, the network measures how fast those blocks actually came and retunes the difficulty up or down to steer the average back toward ten minutes. More mining power makes blocks harder to find, less mining power makes them easier. The ten-minute target holds even as the world's hardware changes.

This is the key idea: Bitcoin does not measure time in clock hours. It measures time in work done. A block is proof that a certain amount of energy was spent, and the chain of blocks is a record of work accumulating in order. That is why the same design also functions as a timeline that no calendar authority sets.

The problem it solves: ordering without a referee

Time matters in money for one blunt reason. If two payments try to spend the same coin at the same moment, someone has to decide which one came first. Whoever makes that call controls the record.

In the traditional system, a bank makes it. The bank is the central timekeeper that stamps each transaction with an order and a moment, and settles which one counts. That works, but it means one party holds the pen. Satoshi Nakamoto's goal was to answer the same question without appointing anyone to hold it.

The Bitcoin whitepaper describes the mechanism as a timestamp server. In its own words, "Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it." Proof of work is what makes this timestamping decentralised. Miners spend real energy to add each block, and once a block is added, "the block cannot be changed without redoing the work." The order of events is set by which chain has the most work behind it, not by which party is trusted. Block height is how deep into that ordered record any given block sits.

It is a fitting detail that Satoshi's own pre-release code did not call this structure a blockchain at all. It called it the timechain, describing it as "a tree-shaped structure starting with the genesis block at the root." The name captures what the height is really counting: not just blocks, but ordered, work-backed time.

Why deeper is safer

Because each block builds on the one below it, height is also a measure of security. To change a transaction buried a few blocks down, an attacker would have to redo that block and every block stacked on top of it, faster than the rest of the network extends the honest chain. The deeper a block sits below the current height, the more accumulated work would have to be beaten.

That work is physical, not symbolic. Every block is proof that real energy was spent, because miners have to burn electricity making guesses until one of them produces a valid block. In August 2026 the whole network runs at roughly 840 exahashes per second, which is about 840 billion billion guesses every second. Rewriting a buried block means re-spending all of that energy for the block itself and for every block layered on top, while out-pacing the entire network as it keeps going. The history is not protected by a rule that says do not change it. It is protected by an amount of energy that no one can realistically gather.

This is what a confirmation is. When your transaction lands in a block, it has one confirmation. Each new block mined on top adds another. Six confirmations is a common convention for treating a payment as settled, because by then the work needed to reverse it is very large. For a fuller walk through that process, see how Bitcoin transactions are verified.

So the same number does two jobs at once. Read forward, height tells you how far the chain has grown. Read backward from the tip, the distance to a given block tells you how firmly its history is locked in. Nothing on paper behaves this way. A ledger entry does not get harder to forge as time passes. A block does.

Block height as Bitcoin's calendar

Once you see height as a clock, a lot of Bitcoin starts to schedule itself by block number instead of by date. The halving, which cuts the new supply of Bitcoin in half, does not happen on a fixed day. It happens every 210,000 blocks. The rules that govern the network are written in the language of height, not the language of the Gregorian calendar.

This is deliberate. A date can be disputed, a clock can be reset, but a block height is agreed on by everyone running the software. It is the one timeline the whole network shares.

For everyday use, block explorers show the current height live, and "block by date" tools translate between the two directions, so you can look up which block was on top at a past moment or estimate when a future height will arrive. As of late August 2026 the chain has passed 964,000 blocks, which is roughly what you would expect from about 144 blocks a day since the start in 2009.

The takeaway

Block height looks like a simple counter, and it is. What makes it powerful is that the count is anchored to physical work and to a strict order. Each step forward cost real energy that has already dissipated as heat and cannot be gathered back, which is what turns a running total into a decentralised clock, a shared calendar, and a depth gauge for how permanent any piece of history has become. When a Bitcoiner points to a block height, they are pointing at a moment that no single party wrote and that no single party can rewrite, because the energy to rewrite it is not there to be spent.

If you want the layer beneath this, start with what a blockchain is and what a hash is. If you want to see where the clock touches Bitcoin's monetary rules, the Bitcoin halving is the clearest example.