Think of a blockchain as a digital ledger. Every page in this ledger is a block. Flipping through the pages reveals the entire history of transactions. But what exactly is printed on each page? What data lives inside a single block? This article opens up a block for you. We will examine its anatomy from the header down to the last byte of transaction data.
A blockchain block has two main parts: the header and the body. The header contains metadata like the timestamp, the hash of the previous block, and the Merkle root. The body holds the validated transactions. This structure ensures immutability, security, and allows anyone to verify the chain’s integrity without relying on a central authority.
The Big Breakdown: Block Header vs. Block Body
Every block ever created on a blockchain follows the same basic blueprint. It has a header and a body. The header is the label. The body is the cargo. This table shows the main differences between these two sections.
| Component | Purpose | Real World Example (Bitcoin) | Typical Size |
|---|---|---|---|
| Block Header | Identifies the block, links it to the chain, and secures the data inside it. | Version, Previous Hash, Merkle Root, Timestamp, Bits, Nonce | 80 Bytes (fixed) |
| Transaction Counter | A simple count that tells the network how many transactions are packed inside. | VarInt (1 to 9 bytes) | ~3 Bytes |
| Block Body | The complete list of transactions that were confirmed in this block. | Coinbase reward + user transfers + smart contract calls | Up to ~4 MB (with SegWit) |
The header is dense with information. The body is where the actual action happens. Let’s break them down piece by piece.
Peeling Back the Block Header
The block header is the engine of trust. It is a tiny piece of data that summarizes the entire block. If the body changes even by one character, the header must change completely. Here is every field you will find inside a standard block header.
- Previous Block Hash: This is the glue. It is the cryptographic hash of the header of the block that came before it. This single field creates the chain.
- Merkle Root: A single hash that represents the full set of transactions in the body. It acts as a fingerprint for the entire transaction list.
- Timestamp: The Unix time when the miner started working on this block.
- Nonce: The “number used once.” Miners change this value billions of times to try and get a valid block hash.
- Bits (Difficulty Target): A compact encoding of the target threshold the block hash must fall under.
- Version: Indicates which set of block validation rules to follow.
How a Miner Builds and Packs a Block
You might wonder how all these pieces actually come together. Here is a simplified step by step look at the process a miner follows.
- Gather transactions. The miner picks transactions from the mempool. They prioritize ones with higher fees.
- Build the Merkle Tree. They pair up the transaction hashes, hash them together, and keep repeating until they get a single Merkle Root.
- Fill the header. They plug in the previous block hash, the Merkle Root, the current timestamp, the difficulty target, and a placeholder Nonce.
- Mine the block. They hash the header. If the hash is above the target, they change the Nonce and try again. This loop runs trillions of times.
- Broadcast. Once a valid hash is found, the miner sends the block to the network. Nodes verify every single field before passing it along.
For a deeper look at how nodes handle this verification, read our guide on
The Body: Where the Transactions Live
If the header is the lock, the body is the treasure. The body of a block contains a complete record of all transactions that were finalized.
The very first transaction in the body is special. On Bitcoin and similar networks, it is called the Coinbase transaction. This is the transaction that creates new coins and awards them to the miner along with the accumulated fees. No signatures are required to spend a Coinbase output because the network rules create that value.
After the Coinbase, you will find the regular transactions. Every transaction includes:
– Inputs (where the coins are coming from).
– Outputs (where the coins are going to).
– Digital signatures (proving ownership).
– Amounts (the value being transferred).
This is the raw data that block explorers display. If you want to follow a single transaction from your wallet all the way into a block, check out
The Magic of the Merkle Tree
The Merkle Root is one of the most elegant parts of block design. It allows you to verify a transaction without storing the entire block.
Lets say a block has 2,000 transactions. The network does not store all 2,000 hashes in the header. Instead, it pairs them, hashes the pairs, and repeats until there is just one hash left. That single hash is the Merkle Root.
If you want to prove that a specific transaction is in that block, you only need a few “sister hashes” to reconstruct the path to the root. You do not need all 2,000 transactions. This is how light wallets work. For a full breakdown of how this hashing works, read
What Makes a Block Immutable?
The chaining of hashes is what makes rewriting history nearly impossible. To change a single transaction in Block 100, you would have to re-mine Block 100, Block 101, Block 102, and every block built on top of it.
“The blockchain is a chain of digital signatures. Each owner transfers the coin to the next by digitally signing a hash of the previous transaction and the public key of the next owner and adding these to the end of the coin.” – Satoshi Nakamoto, Bitcoin Whitepaper
This means the cost of an attack is astronomical. Anyone trying to tamper with a block must outpace the entire network’s hash rate or stake. That is why the longest chain rule is so powerful. If you want to know exactly why this consensus mechanism is needed, see
Do All Blockchains Pack Their Blocks the Same Way?
No. While the general structure is similar, different chains optimize for different things.
Bitcoin blocks are relatively simple. They prioritize security and decentralization. The block size is limited to keep running a full node cheap.
Ethereum blocks are more complex. The header contains extra fields like the State Root, Receipt Root, and Logs Bloom. These fields help smart contracts interact with data after a block is finalized. Ethereum also has a Gas Limit per block, which limits how much computation can happen.
Solana uses a unique structure called Proof of History. Instead of a traditional timestamp, Solana encodes the passage of time directly into the block sequence. This allows for much faster block times.
For a comparison of how these architectures fit into business use cases, read
From Individual Blocks to a Complete Ledger
A single block contains no value. But link enough of them together, and you get an immutable source of truth.
The Previous Block Hash field is what locks the chain together. Block 14,523 contains the hash of Block 14,522. Block 14,524 contains the hash of Block 14,523. This creates a trail of breadcrumbs that goes all the way back to the Genesis Block.
This is the core innovation of distributed ledger technology. It turns a simple container of data into a universal timestamp server. If you are curious about how this technology evolved from hobbyist projects to enterprise solutions, check out
What This Means for Your Next Project
We have popped the hood and looked at every part of a block. It is just a container with a dense header and a packed body. But the way that container is built, linked, and verified changes how we think about trust.
Next time you open a block explorer, you will not just see a random string of letters. You will see the Merkle Root, the Nonce, the previous link, and the hundreds of transactions that make up the chain. Apply this understanding to your own work. Whether you are building a dApp, researching enterprise solutions, or just learning for fun, knowing exactly what is inside a blockchain block is the foundation for everything else in Web3.