A blockchain is a shared, append-only ledger in which transactions are grouped into blocks, each block is cryptographically linked to the one before it, and a network of independent computers agrees on the order of blocks through a consensus mechanism. Because altering any past block would break every link after it, the history becomes practically tamper-evident once enough blocks have been added on top.
In blockchain fundamentals, the key idea is that participants who do not trust each other can still agree on a single version of the data without a central operator. This makes blockchains the foundation of cryptocurrencies, stablecoins, smart contracts and tokenized assets. A blockchain is one specific kind of distributed ledger; not every distributed ledger chains blocks or allows open participation.
How a blockchain stores and links data
A blockchain stores data in blocks, each with a header and a list of transactions. The header contains the hash of the previous block, a summary of the block’s transactions and metadata such as a timestamp. A hash is a fixed-length fingerprint produced by a cryptographic function such as SHA-256 in Bitcoin or Keccak-256 in Ethereum.
The table below lists the main parts of a block and the role each one plays.
| Component | What it contains | Why it matters |
|---|---|---|
| Previous block hash | Fingerprint of the prior block | Creates the chain and tamper evidence |
| Merkle root | Single hash summarizing all transactions | Allows compact proof that a transaction is included |
| Timestamp | Approximate creation time | Orders blocks and adjusts difficulty |
| Consensus data | Nonce, validator signature or similar | Proves the block was produced legitimately |
| Transaction list | Signed transfers or contract calls | The actual recorded activity |
Every transaction is authorized with a digital signature made with the sender’s private key. Nodes verify the signature and check that the sender has enough balance before accepting it, so nobody can spend funds they do not control.
How the network agrees on the next block
Blockchain nodes reach agreement through a consensus mechanism that decides who may add the next block and which chain is valid. In proof of work, miners compete to solve a computational puzzle; in proof of stake, validators who lock up tokens are selected to propose and attest to blocks.
Block timing and confirmation behavior differ considerably between networks. Bitcoin targets one block about every ten minutes, while Ethereum produces a block every twelve seconds and reaches economic finality after roughly two epochs, about thirteen minutes.
| Mechanism | Who adds blocks | Main security basis |
|---|---|---|
| Proof of work | Miners solving hash puzzles | Cost of electricity and hardware |
| Proof of stake | Validators chosen by stake | Value of locked tokens that can be slashed |
| Proof of authority | Approved, identified validators | Reputation and legal accountability |
| Byzantine fault tolerant protocols | Fixed validator set voting in rounds | Honest majority of more than two thirds |
Types of blockchains
Blockchains differ mainly in who may read the data, submit transactions and validate blocks. These choices determine how decentralized, transparent and fast a network can be.
| Type | Who can participate | Typical use |
|---|---|---|
| Public permissionless | Anyone can read, transact and validate | Cryptocurrencies, DeFi, public tokens |
| Private permissioned | One organization controls access | Internal record keeping and testing |
| Consortium | A group of known organizations | Trade finance, supply chains, settlement |
| Layer 2 network | Users of a base chain, with batched settlement | Cheaper and faster transactions |
Public chains offer the strongest censorship resistance but expose all transactions to everyone. Permissioned chains are faster and more private, yet they rely on trust in known operators, which narrows the advantage over a conventional shared database.
Blockchain compared with a traditional database
A blockchain is not a faster or better database; it trades efficiency for the ability to operate without a trusted administrator. The comparison below clarifies when that trade is worthwhile.
| Property | Public blockchain | Centralized database |
|---|---|---|
| Control | Shared among many nodes | Single operator |
| Data changes | Append-only, history preserved | Records can be updated or deleted |
| Throughput | Usually tens to thousands of transactions per second | Often far higher |
| Transparency | Publicly verifiable | Visible only to authorized users |
| Cost per write | Transaction fee paid by the user | Absorbed by the operator |
| Trust model | Cryptography and consensus | Trust in the operator |
A practical test is simple: if all participants already trust one party to run the system, a conventional database is almost always cheaper and faster. A blockchain earns its cost when several parties need a shared record and none should control it alone.
Limitations and misconceptions
Blockchains have real constraints that are often understated. Understanding them prevents misplaced expectations about what the technology can guarantee.
- Garbage in, garbage out: a blockchain proves that data was recorded, not that it was true; off-chain facts need trusted oracles.
- Not truly anonymous: most public chains are pseudonymous, and transaction analysis can often link addresses to people.
- Scalability limits: every full node processes every transaction, which is why fees rise during congestion and layer 2 networks exist.
- Immutability cuts both ways: mistaken transfers usually cannot be reversed, and lost private keys mean permanently lost funds.
- Probabilistic finality: on proof of work chains, recent blocks can still be replaced, so recipients wait for several confirmations.
In simple terms
A blockchain is like a shared notebook that thousands of people keep copies of. New pages are added in order, and every page carries a seal that depends on all the pages before it.
If someone tries to secretly change an old page, the seals no longer match and everyone else notices. That is why nobody needs a single trusted keeper: the group as a whole keeps the record honest.
A practical example
A freelance designer in Kenya is paid by a client in Canada using a dollar stablecoin on a public blockchain. The client signs a transaction with a private key in a wallet app, and the transaction is broadcast to the network’s nodes.
Within seconds, validators include it in a block, and after a short wait the payment is considered final. The designer can check it on a block explorer, which shows the amount, the block number and the number of confirmations. The transaction fee is a small fraction of what an international bank transfer would cost.
No bank in either country operated the ledger, yet both parties trust the outcome because thousands of independent nodes recorded the same block. The designer then converts part of the balance to local currency through an exchange.