Level 1 · Start hereThe village#043

What is a block? One page of the notebook, and the six-line header that locks it

A block is one page of a blockchain: a batch of transactions plus a short header. On Bitcoin the header is 80 bytes and holds six fields, including the previous block's hash and a single fingerprint of every transaction on the page.

The village doesn't write its notebook one line at a time. It waits until there's a batch of payments, writes them all on a fresh page, and then closes the page.

Closing means filling in a small box at the top. Which page came before. A stamp that sums up every line below. The time. And the answer to a puzzle that took a long night to solve. Once the box is filled in, the page is done. Ben arrives the next morning with one more line. Too late: there's no room in a closed box.

That page is a block. The box on top is its header. And the header, not the payments, is what holds a blockchain together.

What it is

A block is one page of a blockchain: a batch of transactions plus a header that describes them. The white paper puts the idea in one line of its network rules: "Each node collects new transactions into a block" (Nakamoto, 2008).

On Bitcoin, the header is tiny. Block headers are "serialized in the 80-byte format" and then hashed (Bitcoin developer reference). Eighty bytes is shorter than this sentence. The transactions underneath can run to a few megabytes.

How it works: the header of block 900,000

Here is a real header, from block 900,000, added on 6 June 2025 (mempool.space). Six fields, in the order the developer reference lists them (Bitcoin developer reference).

  1. Version. A number that tells nodes which set of rules the block follows. Here: 548118528.
  2. Previous block hash. The fingerprint of block 899,999, starting 0000000000000000000196400396be46. This is the link in the chain.
  3. Merkle root. One fingerprint that sums up all 1,562 transactions on the page: 0cfb54e522b07bd1a381adc774ec1851590ef4c3add83958135106534569f970. Change any payment and this line changes. The white paper says transactions are "hashed in a Merkle Tree" with "only the root included in the block's hash" (Nakamoto, 2008).
  4. Time. 1749188499 seconds since 1 January 1970, which is 6 June 2025, 05:41:39 UTC. It's the miner's own clock, so it's approximate.
  5. Bits. 386021236, a coded version of the target the block's hash must be at or below. mempool.space translates it into a difficulty of about 127 trillion. How that number moves is explained in "What is a crypto network?"
  6. Nonce. 2,455,752,826. One of the numbers the miner kept changing until the header's hash came out below the target. It's the answer to the night's puzzle.

Put those six fields together and you get the raw header: 160 hexadecimal characters, which is 80 bytes (mempool.space). Hash it and you get the block's own name, 000000000000000000010538edbf and so on. Block 900,001 quotes that name in its own field 2.

Under the header sits the page itself. 1,562 transactions, 1,920,777 bytes. Bitcoin limits a block by "weight": "The new rule is block weight ≤ 4,000,000" (BIP 141). Block 900,000 weighed 3,130,335, about 78% of the limit. The first transaction on the page pays the miner. mempool.space names the mining pool as ViaBTC (mempool.space).

Why it matters

  • Batches make agreement possible. Thousands of nodes can't agree on every single payment as it arrives. They can agree on one page at a time.
  • The header is the lock. Because field 3 sums up every payment and field 2 points to the previous page, the header's hash depends on everything before it.
  • Space is limited. A block can only hold so much weight. When more people want in than fit, they bid with fees. The page is a waiting room with a doorman.
  • Light wallets read headers. A phone wallet can check a payment against headers without downloading every page, as the white paper's section 8 describes.

Where people get it wrong

  • "A block is a coin." A block is a page of payments. Coins are amounts recorded in those payments.
  • "Blocks hold a fixed number of transactions." They hold a limited weight. Block 900,000 fitted 1,562; a page of simpler payments fits more.
  • "My payment is in the blockchain as soon as I press send." It waits until a miner puts it on a page and that page is accepted.
  • "The timestamp is exact." It's set by the miner, and the rules only keep it within limits.

The sting: read a header yourself

On a block explorer, open any block and look for the fields above: previous block hash, Merkle root, timestamp, bits, nonce. They're all there, usually under "details". Five minutes and you know more about a block than most people who sell courses about blockchains.

Then check the timestamp against the block before it. If anyone tells you a payment was "confirmed" before the page it sits on was even closed, you've found the stranger at the gate. He works fast. The notebook doesn't.

Frequently asked questions

What is a block in a blockchain?

A block is a batch of transactions with a header on top. The header records the previous block's hash, a single fingerprint of all the transactions, the time and the proof of work. Blocks are linked in order to form the blockchain.

What is in a Bitcoin block header?

Six fields in 80 bytes: version, previous block hash, Merkle root, time, bits (the encoded target) and nonce. Hashing the header gives the block's own hash, which the next block records.

What is a Merkle root?

It's one hash that summarises every transaction in a block. If any transaction changed, the Merkle root would change, and with it the block's hash. That lets the header stand in for the whole page.

How big is a Bitcoin block?

Bitcoin limits blocks by weight, to at most 4,000,000 weight units under BIP 141. Block 900,000, from 6 June 2025, weighed 3,130,335 units and took up about 1.9 megabytes.

What is a nonce in a block?

The nonce is a number in the block header that miners change again and again until the header's hash falls below the target. The winning nonce is the visible proof that the work was done.

Sources

  1. Bitcoin developer reference, Block chain (block headers)
  2. mempool.space API, Bitcoin block 900,000 (6 June 2025)
  3. mempool.space API, raw header of block 900,000
  4. mempool.space API, block 900,000 with pool and fee details
  5. Satoshi Nakamoto, Bitcoin: A peer-to-peer electronic cash system (2008)
  6. Eric Lombrozo, Johnson Lau and Pieter Wuille, BIP 141: Segregated Witness (block weight)

Read next.