How Blockchains Work: The Mental Model Every Crypto Trader Needs

What a Blockchain Actually Is

A blockchain is a database. It holds records of transactions, who owns what, and the state of every account. What makes it different from a regular database is the architecture. Instead of one company's server, a blockchain is replicated across thousands of independent computers (called nodes) around the world. Every node holds a complete copy of the database. Every node validates every transaction against a shared set of rules.

The reason anyone cares about this architecture: no single party controls the data. No one can edit records unilaterally. No one can freeze balances except under the rules the network enforces. The database's guarantees come from cryptography and economic incentives rather than from trusting an operator.

The Building Blocks

Transactions

A transaction is a signed instruction. "Address A sends 1 BTC to Address B, signed by A's private key." The signature proves A authorized it. The network verifies the signature and the balance, then adds the transaction to a block.

A blockchain doesn't literally track balances. It tracks transactions. Your "balance" is the sum of transactions minus amounts you've spent. For account-model chains (Ethereum), the node software keeps balance state. For UTXO-model chains (Bitcoin), balance is the sum of unspent transaction outputs assigned to your address.

Blocks

Transactions aren't added one at a time. They're batched into blocks. A block contains:

• Several hundred or thousand transactions
• A timestamp
• A reference to the previous block's hash
• Metadata about the miner/validator who produced the block

The reference to the previous block is what makes it a "chain." Each block's hash is computed over its contents. Changing any transaction in a historical block would change that block's hash, which would invalidate every subsequent block's reference. Rewriting history therefore requires rewriting every block from the change point forward, at a cost equal to all the work that went into those blocks.

Nodes

A node is a computer running blockchain software. Full nodes validate every block and transaction against the consensus rules. They store the entire chain history and relay transactions to peers. Light nodes keep less data and rely on full nodes for validation.

The more independent nodes a blockchain has, the harder it is to coerce the network. Bitcoin has tens of thousands of full nodes worldwide. Ethereum has tens of thousands as well. Smaller chains have fewer, which is one of several centralization risks.

Consensus

Consensus is how nodes agree on which transactions are valid and in what order. A chain fragments the moment nodes can't agree. Consensus mechanisms solve the coordination problem:

• Proof of Work: Miners compete by burning electricity. Winner proposes the next block.
• Proof of Stake: Validators lock up tokens as collateral. Selected validators propose blocks.
• Delegated Proof of Stake: Token holders vote for a small set of validators who propose blocks.
• Byzantine Fault Tolerant (BFT) variants: Committees of validators vote on blocks in rounds.

Different consensus mechanisms make different tradeoffs on security, throughput, decentralization, and finality time.

What Makes Blockchains Different from Databases

A regular database is operated by one entity. That entity can edit any record at any time. Access controls are enforced by the entity. If the entity is compromised, the database is compromised.

A blockchain is operated by many parties following shared rules. No one can unilaterally edit past records. Access control is enforced by cryptographic signatures. If any single node is compromised, the rest of the network is unaffected.

The tradeoffs:

Blockchains don't replace traditional databases. They solve a specific problem: shared record-keeping where no participant trusts any other enough to let them control the data.

Block Times and Finality

Different chains produce blocks at different rates:

Finality is the time required before a transaction is considered permanent. Bitcoin achieves probabilistic finality: the chance of reversal drops exponentially with confirmations. Modern PoS chains often achieve deterministic finality: once a block is finalized, it cannot be reversed without violating consensus rules.

What Blockchains Can and Can't Do

Blockchains can:

• Record transactions with high confidence they won't be reversed
• Execute smart contract code deterministically across nodes
• Enforce ownership and transfer rules without a central operator
• Provide verifiable audit trails of asset movement
• Settle transactions globally without traditional banking rails

Blockchains can't:

• Handle hundreds of millions of transactions per second (current ceiling is in the tens of thousands, not counting scaling solutions)
• Store large amounts of data cheaply (on-chain storage is expensive)
• Know anything about the real world without oracles (the chain is sealed off from external data)
• Reverse transactions (there's no undo, even for legitimate mistakes)
• Prevent social-engineering attacks (if you authorize a bad transaction, the chain will execute it)

Chain Categories

Layer 1 (L1): Base blockchains that provide security and consensus. Bitcoin, Ethereum, Solana, Cardano are L1s.

Layer 2 (L2): Protocols built on top of an L1 to extend throughput or add features. Arbitrum and Optimism are Ethereum L2s. Lightning Network is a Bitcoin L2. See our guide to Layer 1 vs Layer 2.

Sidechains: Independent chains pegged to an L1 but with their own consensus. Polygon PoS and many others.

Specialized chains: Bitcoin for settlement. Ethereum for programmability. Solana for throughput. Monero for privacy. Each makes design tradeoffs that others don't.

Related Intelligence

• Proof of Work: The consensus mechanism securing Bitcoin.
• Proof of Stake: The consensus mechanism securing most modern chains.
• Layer 1 vs Layer 2: How scaling solutions are layered on top of base chains.
• Blockchain explorers: Tools for inspecting the ledger directly.