What is the Block Header?

While a Bitcoin block can physically weigh several megabytes and contain thousands of transactions, its identity is condensed into a tiny, elegant 80-byte package called the Block Header.

The block header is the most critical piece of metadata in the entire Bitcoin network. It is what miners hash during Proof of Work, what light clients download to verify transactions, and what binds the historical chain together.

---

🗃️ The 6 Fields of the 80-Byte Header

A block header is comprised of exactly six fields, serialized in binary format. Here is the precise anatomical breakdown:

Field Number	Field Name	Size (Bytes)	Data Type	Purpose
1	Version	4	int32_t	Indicates software version/upgrade features (e.g., SegWit signaling).
2	Previous Block Hash	32	char[32]	The SHA-256 hash of the parent block's header. This forms the chronological link.
3	Merkle Root Hash	32	char[32]	A single 32-byte cryptographic hash summarizing every transaction in the block.
4	Timestamp	4	uint32_t	Unix epoch time indicating approximately when mining on the block began.
5	Difficulty Target	4	uint32_t	The threshold target coded in "Bits" format that the header hash must fall below.
6	Nonce	4	uint32_t	A counter variable miners increment to modify the block header hash during Proof of Work.

┌────────────────────────────────────────────────────────┐
│                   80-BYTE BLOCK HEADER                 │
├───────────┬───────────────────┬─────────────┬──────────┤
│ Version   │ Previous Hash     │ Merkle Root │ Time etc │
│ (4 Bytes) │ (32 Bytes)        │ (32 Bytes)  │ (12 B)   │
└───────────┴───────────────────┴─────────────┴──────────┘

---

🔍 Deep Dive into the Header Fields

1. Version (4 Bytes)

The version field is used by miners to signal support for soft fork upgrades. By changing specific bits within this 4-byte field (a process called Version-Bits signaling), the network can coordinate upgrades like SegWit or Taproot without splitting the chain.

2. Previous Block Hash (32 Bytes)

This is the hash of the parent block header. Because this hash is embedded inside the 80-byte header, it is impossible to change any transaction in the previous block without completely invalidating the current block and all blocks that follow it.

3. Merkle Root Hash (32 Bytes)

Rather than writing all 3,000 transactions directly into the block header (which would make headers huge), they are mathematically structured into a binary hash tree called a Merkle Tree. The single resulting 32-byte hash—the Merkle Root—is stored in the header. If even a single satoshi of a single transaction changes, the Merkle Root changes entirely.

4. Timestamp (4 Bytes)

The timestamp is written in standard Unix epoch time (the number of seconds since January 1, 1970). To prevent malicious miners from gaming the system, the network consensus rules require that a block's timestamp must be greater than the median of the previous 11 blocks, and less than 2 hours into the network's future.

5. Difficulty Target / Bits (4 Bytes)

This 32-bit field is a compact representation of the 256-bit cryptographic target. In Bitcoin's codebase, it is called Bits. It specifies how difficult the Proof of Work puzzle is. The hash of the block header must be mathematically less than this target to be accepted by nodes.

6. Nonce (4 Bytes)

The word Nonce stands for "number used once." It is a simple counter that starts at 0. A miner hashes the 80-byte header, checks if the hash is below the target, and if not, increments the Nonce by 1 and hashes again. Since the Nonce is 4 bytes, it has a range of $2^{32}$ (approx. 4.29 billion) possibilities. If a miner exhausts all 4.29 billion nonces, they alter the Coinbase transaction's extra-nonce field to change the Merkle Root, and start the counter again.

---

⚡ Why are Headers Kept Lightweight?

By keeping the block header capped at exactly 80 bytes, Bitcoin achieved unparalleled efficiency: * Light Clients (SPV): Lightweight wallets on mobile phones do not need to download gigabytes of raw transaction data. They only download the 80-byte block headers. Downloaded headers for 10 years of Bitcoin history require less than 50 megabytes of storage, allowing mobile devices to run trustlessly. * ASIC Hashing Efficiency: Mining chips (ASICs) only need to load the tiny 80-byte block header into their ultra-fast on-chip memory registers to perform hashing loops, maximizing hash rates and energy efficiency.