In Part 1 of this series, you got the vocabulary: what crypto actually is, where it came from, and why people keep confusing the technology with the speculation around it. That foundation matters here, because this article goes one layer deeper. Blockchain is the machine underneath everything. Understanding it changes how you think about trust, ownership, and the way records work.
Most people hear "blockchain" and think Bitcoin. Some think Ethereum. A few think it's a company somewhere. None of that is quite right. Blockchain is infrastructure. It's the protocol, not the product. Calling blockchain "Bitcoin" is like calling TCP/IP "email." The relationship is real, but the categories are completely different.
A Filing Cabinet Nobody Owns
A blockchain is a filing cabinet that the whole world shares and nobody owns. That sentence is doing a lot of work, so it's worth sitting with it before moving on.
Why the hook matters
The filing cabinet image isn't decorative. It's structural. A filing cabinet stores records in order. You can open any drawer, read any document, and trace the history of any entry. A blockchain does exactly that, except no single person controls the cabinet, no single building houses it, and no single government can confiscate it. Those aren't features someone bolted on for marketing. They're properties that emerge directly from how the system is built.
Blockchain is also not inherently financial. That association came from Bitcoin being the first major application. The underlying technology doesn't care what kind of data you put in it.
What this article covers
This article unpacks four concepts: blocks, chains, hashing, and consensus. No investment talk. No price predictions. Just the mechanical curiosity of how a system this strange actually holds together.
You're in Part 2 of 8
This series builds sequentially. Part 1 covered what cryptocurrency is and where it came from. By Part 8, you'll have a complete picture of how the whole ecosystem functions, from the protocol level up to wallets, exchanges, and regulation.
What Is a Block, Really?
A block is a container. That's the simplest accurate description. It's a structured bundle of data, packaged according to rules the network agrees on, sealed with a unique identifier, and added to a growing sequence of other containers just like it.
Anatomy of a single block
Think of a block as a page in a ledger book. Every page has the same format: a header at the top with metadata, a body with the actual records, and a timestamp marking when the page was filled. Blocks follow the same pattern.
The header holds administrative information: the block's own hash, the hash of the previous block, a timestamp, and a number called the nonce that matters during the mining process. The data payload is the main content. The timestamp records when the block was created and accepted by the network.
In Bitcoin's case, the payload is a list of transactions. Alice sent 0.3 BTC to Bob. Carol sent 1.1 BTC to Dave. Hundreds of those records get bundled together into one block approximately every ten minutes.
What kinds of data live inside
Other blockchains store different things entirely. Ethereum blocks contain smart contract instructions. Some blockchains store NFT ownership records. Experimental systems have stored votes, medical record hashes, and supply chain checkpoints. The block structure is flexible. The enforcement mechanism is what stays consistent.
One important constraint: blocks have size limits. Bitcoin's effective limit sits around 1 to 4 megabytes depending on how you count. That limit exists to keep blocks small enough that ordinary computers can download and verify them without specialized hardware. Bigger blocks mean faster throughput but higher barriers to participation. It's a deliberate tradeoff, not an oversight, and it's been one of the most contested design decisions in Bitcoin's history.
A block by itself is just a record. Useful, but not particularly special. The chain is what gives it permanence.
Hashing: The Fingerprint System
Before you can understand why the chain is tamper-resistant, you need to understand hashing. It's the mechanism that makes everything else work.
What a hash function does
A hash function takes any input, a word, a sentence, an entire novel, a transaction record, and produces a fixed-length string of characters as output. That output is called a hash or digest. The same input always produces the same hash. Different inputs produce different hashes. And here's the part that matters most: you cannot work backwards from the hash to reconstruct the original input.
That last point is not a limitation of current computing power. It's a mathematical property of the function itself. The process is genuinely one-way.
Why fingerprints, not encryption
People sometimes call hashing a form of encryption. It isn't. Encryption is a two-way process. You encrypt data with a key, and someone with the right key can decrypt it back to the original. Hashing has no key, no reverse, no decryption step. It's a one-way transformation.
The fingerprint analogy is more accurate. A fingerprint is unique to a person and consistent every time you take it. But looking at a fingerprint tells you nothing about what the person looks like, how tall they are, or what their name is. The hash is the fingerprint of the data. Unique. Consistent. Irreversible.
Bitcoin uses an algorithm called SHA-256 (Secure Hash Algorithm, 256-bit output). Every hash it produces is exactly 64 hexadecimal characters long, regardless of whether the input was three words or three million.
Try it yourself: the avalanche effect
This is where hashing gets genuinely surprising. Change one character in the input, and the output changes completely. Not slightly. Completely.
| Input | SHA-256 Hash (first 20 chars) |
|---|---|
hello | 2cf24dba5fb0a30e... |
Hello | 185f8db32921bd46... |
One capital letter. Entirely different hash. This property is called the avalanche effect, and it's not a bug. It's a feature. It means that any attempt to alter a record, even a tiny, subtle alteration, produces a completely different fingerprint. The change cannot be hidden.
Why this matters for tamper detection
If a block's data changes even slightly, its hash changes entirely. Any system that stores and compares hashes will immediately detect the discrepancy. You don't need to read the data to know it's been altered. You just need to check the fingerprint.
Chaining the Blocks Together
Here's where the structure earns its name. Each block doesn't just contain its own data. It contains the hash of the previous block. That single design decision is what turns a list of records into a chain.
The previous hash pointer
Think of interlocking rings, except each ring is stamped with an impression of the ring before it. If you reshape any ring, the impression it left on the next ring no longer matches. The mismatch is immediately visible. That's exactly how block chaining works.
Block 48 contains the hash of Block 47. Block 49 contains the hash of Block 48. Every block in the chain carries a reference to its predecessor, all the way back to the very first block.
That first block is called the genesis block. It has no previous hash to reference, so that field is filled with zeros by convention. Bitcoin's genesis block was created in January 2009. It's still sitting at position zero in the chain, unchanged and unchangeable.
Why breaking one block breaks everything after it
Suppose someone wants to alter a transaction in Block 47. They change the record, which changes Block 47's hash. But Block 48 was built to reference Block 47's original hash. Now Block 48's stored reference doesn't match Block 47's actual hash. Block 48 is broken. And Block 49, which references Block 48, is broken by extension. Every block after the altered one becomes invalid.
This is why blockchain history is described as immutable. Not because the data is physically impossible to change, but because changing any record requires recomputing every subsequent block, and then convincing the rest of the network to accept your rewritten version over the legitimate one. The chain structure makes that task computationally enormous.
Immutability is a property of the structure working together with the network. The structure alone isn't enough. The network has to enforce it. That's where consensus comes in.
The Distributed Ledger: Thousands of Copies
The chain structure prevents quiet tampering. Distribution prevents any single actor from controlling the chain in the first place.
Nodes and what they do
A node is any computer participating in the blockchain network. A full node downloads and stores a complete copy of the entire blockchain, validates every new block against the rules, and relays valid transactions to other nodes. Right now, thousands of full nodes are running Bitcoin's blockchain simultaneously, spread across dozens of countries.
Go back to the filing cabinet. Except now the cabinet exists in 19,000 locations simultaneously. Every location has an identical, complete copy. No single location is the "real" one. They're all equally real, and they're constantly checking each other.
Why distribution matters for trust
A centralized database is only as trustworthy as the organization running it. If the organization lies, the record lies. If the server goes down, the record disappears. If a government compels the operator to alter records, the records change.
A distributed ledger changes that equation. To alter the record, you'd need to alter the majority of copies simultaneously, faster than the network can detect and reject the change. That's not impossible in theory, but it's expensive enough in practice that it hasn't happened to Bitcoin's main chain.
The tradeoff is real. Distribution creates resilience, but it also creates complexity. Nodes sometimes disagree about which version of the chain is correct. Processing is slower than a centralized database. Coordination takes time. These aren't flaws to be embarrassed about. They're the cost of the properties the system is designed to have.
When nodes disagree, the network needs a way to resolve the conflict and settle on one authoritative version. That resolution process has a name.
Consensus: How Strangers Agree on One Truth
Thousands of anonymous participants. No central authority. No phone number to call when something goes wrong. The question isn't just how they communicate. It's how they agree.
The core problem consensus solves
Every full node holds a copy of the blockchain and validates incoming transactions independently. When a new block is proposed, nodes need to decide: is this block legitimate? Should it be added to the chain? If half the network adds it and half rejects it, you end up with two competing versions of history. That's a problem.
Consensus mechanisms are the rules the network uses to reach agreement without a referee. They define what counts as a valid block, who gets to propose one, and how the network resolves disagreements when they arise. Consensus is what removes the need for a trusted central authority. It replaces institutional trust with mathematical and economic incentives.
Consensus is not voting
Consensus mechanisms aren't simple majority votes. They're structured processes that make it expensive to cheat and profitable to cooperate honestly. The incentive structure is part of the design, not an afterthought.
The Byzantine Generals problem, briefly
The theoretical foundation for this challenge has a name: the Byzantine Generals problem. Imagine several generals surrounding a city, communicating only by messenger. They need to agree on whether to attack or retreat. Some generals might be traitors sending false messages. The question is: can the loyal generals reach reliable agreement despite the presence of bad actors they can't identify?
Computer scientists Leslie Lamport, Robert Shostak, and Marshall Pease formalized this problem in 1982. Satoshi Nakamoto's 2008 white paper proposed a practical solution for a financial network.
"The network is robust in its unstructured simplicity. Nodes work all at once with little coordination. They do not need to be identified, since messages are not routed to any particular place and only need to be delivered on a best effort basis."
. Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System, 2008
The key insight is that you don't need to identify or trust individual participants. You need to make honest participation more rewarding than dishonest participation, at scale, for strangers, forever.
There are multiple ways to implement that idea. Bitcoin uses one approach. Ethereum switched to another in 2022. Newer blockchains have introduced additional variations, each with different tradeoffs between security, speed, and energy consumption. Part 3 covers exactly that: Proof of Work and Proof of Stake, what they actually do, and why the difference matters more than most coverage suggests.
Proof-of-Work: Earning the Right to Write
Part 1 of this series established the basic structure of a blockchain: blocks of data, linked by hashes, distributed across a network of nodes. That structure explains what a blockchain is. This section explains how it decides who gets to add the next block.
What miners actually do
Nobody just volunteers to write the next block. The right to write has to be earned, and in Bitcoin's design, it's earned through computation.
Proof-of-Work is a competition. Thousands of computers around the world race to solve the same puzzle simultaneously. The puzzle isn't clever math or a logic problem. It's brute force: find a number called a nonce that, when combined with the block's data and fed through SHA-256, produces a hash that falls below a specific target value.
Think of it like rolling an enormous set of dice and needing to land under a certain number. Each roll takes almost no time. But the target might require you to roll under 1 in 10 trillion. You just keep rolling until you get lucky, and "lucky" takes, on average, an enormous number of tries.
The miner who finds a valid nonce first broadcasts the new block to the network. Every other node verifies the solution instantly because checking a hash is trivial. One hash computation, one comparison. That asymmetry is the point: hard to find, easy to verify.
The winning miner collects the block reward, currently 3.125 BTC per block following the April 2024 halving, plus any transaction fees included in that block.
Why energy expenditure creates trust
The energy spent isn't waste in the protocol's logic. It's the cost of participation. A miner who cheats, submitting an invalid block, loses the electricity they spent. There's no refund. That cost is what makes the system trustworthy without requiring anyone to trust anyone else.
The 51% attack explained simply
Control more than half of the network's total computing power and you can, in theory, rewrite recent history. You could reverse transactions you made, spend the same coins twice. This is the 51% attack.
In practice, on Bitcoin's network, acquiring 51% of the hash rate would require billions of dollars in specialized hardware and ongoing electricity costs. The attack would also destroy confidence in the network, crashing the value of the very asset you'd be trying to steal.
Energy Note
Bitcoin's annual electricity consumption is estimated at roughly 120 to 150 terawatt-hours, comparable to the annual usage of a mid-sized country. This is a factual characteristic of the design, not an accident.
Proof-of-Stake: Voting With Collateral
Not every blockchain uses computation as its trust mechanism. Proof-of-Stake takes a different approach: instead of spending electricity to earn the right to write, you lock up cryptocurrency as collateral.
Validators vs miners
In a Proof-of-Stake system, participants called validators deposit a specified amount of crypto into a smart contract. That deposit is their stake. The protocol selects validators to propose and attest to new blocks through a weighted-random process: the more you've staked, the higher your probability of selection. There's no race. There's no computation arms race. Selection happens algorithmically, and the work of producing a block is straightforward once you're chosen.
Ethereum requires 32 ETH to run a solo validator node. Smaller holders can participate through staking pools that aggregate deposits across many users.
Ethereum's 2022 switch from Proof-of-Work to Proof-of-Stake, called The Merge, is the most prominent real-world example of a network changing consensus mechanisms mid-operation. The transition had been planned for years and executed without downtime.
Slashing and why it keeps validators honest
The question Proof-of-Stake has to answer is: what stops a validator from lying? In Proof-of-Work, the answer is wasted electricity. In Proof-of-Stake, the answer is slashing.
If a validator acts dishonestly, such as signing two conflicting blocks at the same height, the protocol destroys a portion of their staked collateral. The stake they locked up is partially or fully burned. The economic threat replaces the physical one.
Other consensus variants worth knowing
Several other mechanisms exist, each with different trade-offs. Delegated Proof-of-Stake lets token holders vote for a smaller set of delegates who do the validating. Proof-of-Authority uses pre-approved validators, common in private networks. Proof-of-History, developed by Solana, encodes a cryptographic timestamp sequence to order events efficiently. Proof-of-Space uses allocated disk storage rather than computation or collateral as the scarce resource. Each of these solves the same core problem differently: who gets to write, and why should everyone else trust them.
What Makes a Blockchain 'Public' vs 'Private'?
The word "blockchain" covers a wide range of systems with fundamentally different trust models. Grouping them all together causes real confusion.
Permissionless vs permissioned chains
A public blockchain is open to anyone. Anyone can run a node, submit a transaction, or become a validator or miner. No one controls access. Bitcoin and Ethereum are the clearest examples. The rules are enforced by math and economic incentives, not by institutions or contracts.
A private or permissioned blockchain restricts who can participate. A company or consortium controls access. Participants are known and vetted. Hyperledger Fabric, widely used in enterprise supply chain and financial applications, operates this way. It's a blockchain in structure but not in spirit: the trust comes from the institution running it, not from the protocol itself.
Consortium blockchains sit in the middle. Multiple organizations share control jointly. No single entity dominates, but the network isn't open to the public either. Several banking consortia and trade finance networks use this model.
Quick Distinction
When most people say "crypto," they mean public blockchains. When most enterprises say "blockchain," they often mean permissioned systems. These are different tools solving different problems, and conflating them creates unnecessary confusion.
Where enterprise blockchains fit in
Private chains trade decentralization for speed, privacy, and compliance. They can process transactions faster because they don't need global consensus across thousands of anonymous nodes. They're useful for specific business contexts. They're not the same thing as Bitcoin, and they don't share Bitcoin's properties or guarantees.
Common Misconceptions, Cleared Up
These aren't gotchas. A lot of smart people hold these beliefs because the information environment around crypto is genuinely noisy.
Blockchain is not Bitcoin
Bitcoin is one application built on one blockchain. Blockchain is the underlying data structure and protocol design. Saying they're the same is like saying the internet and Facebook are the same thing. Bitcoin was the first major blockchain, which is why the names got tangled together early on.
Immutable does not mean perfect
The blockchain protocol itself is extremely difficult to alter. But everything built on top of it is software, and software has bugs. Smart contracts have been exploited for hundreds of millions of dollars. Exchanges have been hacked. Wallets have been compromised through phishing. The ledger records transactions accurately; it doesn't guarantee that the transactions were ones you wanted to make.
Decentralized does not mean anonymous
Public blockchains are pseudonymous, not anonymous. Every transaction is permanently visible to anyone. Wallet addresses aren't names, but they're traceable. Chain analysis firms specialize in connecting addresses to real-world identities, and they're quite good at it. If you've ever moved crypto through a regulated exchange that collected your identity, that connection exists.
One more worth mentioning: you don't need to understand blockchain to use crypto, just as you don't need to understand TCP/IP to browse the web. Most users never interact with the protocol layer directly. Understanding it anyway puts you in a much better position to evaluate what you're actually using.
Your Blockchain Basics Checklist
What you should now be able to explain
If you've read both Part 1 and this installment, you should be able to walk someone through these concepts without notes.
If any of those felt shaky, Part 1 covers the foundational layer: blocks, hashes, and nodes. It's worth a reread before moving forward. The concepts in this series build on each other, and a gap in the foundation shows up later.
Coming Up in Part 3
Part 3 moves up the stack from infrastructure to ownership. Wallets, public and private keys, and how the network knows a transaction actually came from you.
The Foundation Is Set. What Comes Next
Recap of what this part covered
Four pillars. Blocks hold the data. Hashing fingerprints it. Chaining locks the sequence. Consensus decides who writes next and makes sure everyone agrees.
The shared filing cabinet no one owns isn't just a metaphor anymore. You now understand the structural reasons it works the way it does. Proof-of-Work makes writing expensive. Proof-of-Stake makes dishonesty expensive. Both approaches arrive at the same destination through different routes.
Where Part 3 takes you
The infrastructure is understood. Now the interesting question is: how does the network know something belongs to you? Part 3 covers wallets, public and private keys, and the cryptographic process that turns a signature into proof of ownership. It's the part most people skip, and it's the part that explains nearly every costly mistake people make with crypto.
You've covered material that most participants in this space have never worked through carefully. That matters.
