Skip to content
Blockchain & Web3All explainers

What is blockchain? How it works, explained

A blockchain is a shared, append-only ledger replicated across many computers that agree on its contents through consensus. Here is how blocks, hashing, and consensus work, plus the trade-offs it forces.

Published: Updated: Reading time: 7 min
On this page

Blockchain is a shared, append-only ledger copied across many independent computers that agree on its contents through a consensus mechanism. In plain terms, it's a distributed ledger no single party owns: once a transaction is written and confirmed, rewriting it becomes cryptographically and economically impractical.

How does blockchain work

Picture a spreadsheet that thousands of computers keep at once. A new transaction is broadcast to the network, bundled with others into a block, and checked by every participant. Once the network agrees, the block goes on the end of the chain and each computer updates its own copy. There's no head office signing off; the shared agreement decides what counts.

Those computers are called nodes. A full node stores the entire ledger and checks every rule itself, so it doesn't have to trust anyone else's word.

Ownership works differently too. You don't log in with a username and password. You control funds with a private key held in a crypto wallet, and whoever holds the key holds the asset.

All of this is slower than a normal database, and that's deliberate. Every full node validates every block and keeps its own copy of the ledger, so you pay in speed for not having to trust a single operator.

Blocks, hashing, and why the chain is hard to rewrite

Each block holds a batch of transactions plus a cryptographic hash of the block before it, a chaining design described in the NIST IR 8202 Blockchain Technology Overview. A hash is a fixed-length fingerprint of some data. Feed it the same input and you always get the same output. Change a single character and the output looks completely different.

That linking is what makes the ledger tamper-evident. Say you edit a transaction buried ten blocks deep. Its hash changes, no longer matches the fingerprint recorded in the next block, and breaks every link after it, all the way to the tip, so the network rejects the tampered copy. To make the edit stick, you'd have to recompute every block from your change to the present, faster than the rest of the network extends the honest chain. On a large network that isn't realistic, which is what people mean when they call blockchains immutable.

Blockchain consensus mechanisms: proof of work vs proof of stake

Consensus is the rule that decides which block the network accepts next, and it's where the security actually lives. Two mechanisms dominate.

  • Proof of Work (PoW): miners race to solve a hard math puzzle, and the first to solve it proposes the next block and earns a reward. Solving costs real electricity, so the honest chain is the one with the most accumulated work, as the Bitcoin whitepaper lays out. Bitcoin produces a block roughly every 10 minutes, and the block subsidy has been 3.125 BTC since the April 2024 halving, with transaction fees paid on top.
  • With Proof of Stake (PoS), validators are picked based on collateral, not electricity. You lock up the network's token as a bond, get chosen to propose or attest to blocks, and lose part of your stake if you try to cheat. Ethereum switched from PoW to PoS on 15 September 2022, an upgrade called the Merge, which cut Ethereum's own energy use by about 99.95%.
Proof of WorkProof of Stake
Who adds blocksMiners spending computing powerValidators who lock up tokens
Energy useHighLow
Penalty for cheatingWasted electricitySlashed stake
Best-known exampleBitcoinEthereum since 2022

Neither is strictly better. Proof of Work has the longest track record and a security model that's easy to reason about, but it burns a lot of energy. Proof of Stake is far greener, and on Ethereum it brings a clear finality point that PoW's probabilistic confirmations lack, though critics argue it can concentrate influence among the largest stakers. You'll also run into delegated Proof of Stake, where token holders vote for a small set of validators, and Byzantine fault tolerant engines such as CometBFT, used by many Cosmos chains and by permissioned networks.

Public vs private blockchains

Not every blockchain is open to the world.

A public, permissionless blockchain lets anyone join. You can run a node, read the full ledger, and send transactions without asking permission or proving who you are. Bitcoin and Ethereum work this way, and that openness is both their censorship resistance and their performance ceiling.

A private, permissioned blockchain restricts who can participate. A known group of organizations decides who validates and who reads what, which suits partners who want a shared, tamper-evident record kept off the open internet. Hyperledger Fabric is one framework built for this kind of consortium setup. That said, if a small group already controls access, a well-run shared database may do the same job with less overhead, and it's worth checking that before committing.

What blockchains are good and bad at

Blockchains make sense when several parties who don't fully trust each other need one shared source of truth with no referee in the middle. Settlement between institutions, provenance tracking, programmable smart contracts, and moving value across borders without a bank (the base of most DeFi) all fit that shape.

They're a bad fit when you control all the data yourself, need high throughput, or want the option to delete records. Bitcoin handles only a handful of transactions per second, and Ethereum's base layer has historically managed roughly 15 to 20. Visa, by comparison, says VisaNet can process more than 65,000 transaction messages per second. If a plain database would serve your use case, it's almost always faster, cheaper, and simpler. Use a blockchain when removing the trusted middleman is the real requirement. If you're at that point, our blockchain development services team can help you weigh throughput, consensus security, and where the data should live.

Layers and networks

Layer 1 networks such as Bitcoin and Ethereum provide the base security and settle transactions directly on-chain. Block space there is scarce and fees rise with demand. Layer 2 networks sit on top, batching many transactions off-chain and posting compressed proofs back down to Layer 1. You get much higher throughput and far lower fees while still relying on the base layer's security, which is why a large share of routine Ethereum activity now runs on Layer 2 rollups.

Common misconceptions

  • "Blockchain equals Bitcoin." Bitcoin was first, but it's one network among thousands. Blockchain is the underlying pattern.
  • "It's completely anonymous." Most public chains are pseudonymous, not anonymous. Your name isn't attached, but every transaction is permanently visible and often traceable back to a real identity through an exchange.
  • "Data on a blockchain can't be wrong." Immutability protects a record after it's written. It does nothing to guarantee the record was true going in, and a false entry stays on the chain just as firmly as a true one.
  • "It's free and instant." Public networks charge fees and take time to confirm, and both can climb sharply during congestion.

So blockchain is a narrow tool: it keeps a shared record honest when no one is in charge. If your problem looks like that, it's worth the overhead. If it doesn't, an ordinary database will usually serve you better.

Frequently asked questions

  • Consensus is the rule that decides which new block everyone accepts next. Proof of Work makes miners spend real computing power to earn that right, so the honest chain is the one with the most work behind it. Proof of Stake instead picks validators who have locked up collateral and lets them vote, and anyone caught cheating loses part of that stake through slashing. Either way, no central server decides.

  • Each block carries a cryptographic hash of the block before it, so the blocks are chained by their fingerprints. Change one old transaction and its hash changes, which breaks every link after it and the network rejects the tampered copy. On a busy Proof of Work chain, rewriting history also means redoing all that work faster than everyone else combined, which is why people call it immutable in practice.

  • A public blockchain like Bitcoin is permissionless. Anyone can run a node, read the ledger, and transact without asking anyone. A private, or permissioned, blockchain restricts who can join and validate, so a known group of organizations controls access. Enterprises often pick permissioned networks such as Hyperledger Fabric when they want shared record-keeping among partners without opening the ledger to the public internet.

  • No. Bitcoin is one blockchain, the first widely used one. Blockchain is the underlying idea, a shared ledger secured by consensus, and thousands of networks use it for things that have nothing to do with Bitcoin, from Ethereum smart contracts to supply-chain tracking. Every Bitcoin is recorded on a blockchain, but not every blockchain has anything to do with Bitcoin.

  • A node is any computer running the network's software and keeping a copy of the ledger. Full nodes store the whole chain and check every rule themselves, so nobody has to take a central authority's word for anything. More independent nodes make the network harder to censor or rewrite.

Still unanswered
Ask us directly

A senior engineer replies under 4 hours.

Related expertise