Understanding Blockchain: Definition, Types, Block Components, and Bitcoin Block Structure

Blockchain originated from the 2008 Bitcoin whitepaper by Satoshi Nakamoto and is essentially a decentralized, cryptographically secured ledger that uses distributed consensus to maintain a database without a central administrator.

The technology consists of underlying protocols, peer‑to‑peer communication, consensus mechanisms, cryptography, and timestamp servers, with the core innovation being the combination of blocks, chains, and timestamps.

Blockchains are categorized into three types:

Public blockchains: anyone can send transactions, participate in consensus, and record data.

Consortium (industry/organization) blockchains: a selected set of nodes (e.g., via DPOS) handle consensus and recording, while all nodes can send transactions.

Private blockchains: the ledger and consensus are controlled by a single entity or organization.

Each block is analogous to a train carriage, composed of a fixed‑size block header (e.g., 80 bytes) that stores metadata such as version, timestamp, difficulty, nonce, previous block hash, and Merkle root, and a variable‑size block body that contains the actual transaction data.

The first block, called the genesis block, was created by Satoshi Nakamoto on January 3 2009 and contains the immutable message: “The Times 03/Jan/2009 Chancellor on brink of second bailout for banks.”

Blocks can store any data required by the upper‑layer application; cryptocurrencies like Bitcoin are merely one use case of the underlying distributed ledger.

Bitcoin’s block structure includes:

Block Header : version (4 bytes), timestamp (4 bytes since 1970‑01‑01 UTC), difficulty target (4 bytes), nonce (4 bytes), previous block hash (32 bytes), and Merkle root hash (32 bytes).

Block Body : magic number (identifies the network, e.g., 0xD9B4BEF9 for mainnet), block size (4 bytes), transaction count (1‑9 bytes), and variable‑length transaction details stored as a Merkle tree.

Transactions represent value transfers, are broadcast to all nodes, and must be validated before being included in a block; each transaction’s inputs reference outputs from previous transactions (except coinbase transactions).

Future articles will cover consensus mechanisms and Bitcoin’s UTXO model.