A blockchain in one sentence
A blockchain is a continuously growing list of transaction batches, called blocks, that are linked together so tightly by cryptography that altering any past block would break the chain. The list is stored in many copies on computers around the world, and a public rulebook decides which copies count. That combination — append-only history, shared storage, public rules — is what makes a blockchain different from any database you have used before.
The mental shortcut: a normal database has an admin who can edit any row. A blockchain has no admin, only nodes and rules. If your transaction gets added, the entire network just collectively decided it follows the rules; nobody could quietly override that.
Block by block: what a chain actually is
Strip the buzzwords away and a blockchain is three ideas stacked: blocks, hashes and a chain.
The block
A block is a small package of data. It contains a list of recent transactions (people sending coins, calling smart contracts, etc.), a timestamp, and a piece of bookkeeping. New blocks are produced on a schedule — every ten minutes on Bitcoin, every twelve seconds on Ethereum — and once a block is published, it is broadcast to the whole network.
The hash
Each block carries a hash, a short string of characters that acts as the block's fingerprint. The hash is computed from everything inside the block, including the previous block's hash. If you changed a single character anywhere in the chain — even from years ago — the resulting hashes would no longer match and every honest node would notice instantly. This is how the chain is bound together. We go deeper on the cryptography in our what is a hash guide.
The chain
Because every block references the previous block's hash, the entire history is linked in one direction, from the very first block (the genesis block) to the most recent. To rewrite a transaction from a year ago you would need to re-mine or re-stake every block since, faster than the rest of the network is producing new ones — which on a serious chain is economically impossible.
Nodes: the network behind the chain
The chain itself is just data. It is the network of nodes that keeps it alive. A node is a computer running the blockchain's software and storing a copy of the entire chain. Anyone can run one. There is no head office.
Nodes do three things constantly. First, they receive new transactions from wallets and forward them around. Second, they verify each new block against the rules — checking signatures, balances, hash linkage, and whatever else the protocol requires — and reject anything that fails. Third, they share their view of the chain so newcomers and disconnected nodes can sync. The more independent nodes a network has, in different countries, on different hardware, the harder it is to censor, capture or shut down.
Not every node produces blocks. On Bitcoin, only miners produce blocks; on Ethereum, only validators do. The vast majority of nodes are just watchers — they store the chain, verify everything, and serve queries. That distinction matters, because anyone can be a watcher without buying special hardware or putting up capital.
Consensus: how the network agrees on history
If anyone can produce a block, who decides which one is real? This is the consensus problem, and it is the core technical challenge a blockchain solves. There are two main families of answer.
Proof of work
Used by Bitcoin and a few others. Producing a block requires solving a computational puzzle that costs a lot of electricity. The first to find a valid solution gets to extend the chain and is rewarded. To rewrite history you would need to redo all that work faster than the rest of the network — which would cost so much that attacking is not worth the prize. Our what is proof of work guide covers the trade-offs in detail.
Proof of stake
Used by Ethereum, Solana, Cardano and most newer chains. Instead of burning electricity, block producers — called validators — lock up a deposit of the network's coin. The protocol picks them in proportion to their stake. Cheating gets the stake destroyed (called slashing), which makes attacks economically self-defeating. Our what is proof of stake guide goes deeper on the mechanics and trade-offs.
Both work. They have different cost structures, different attack surfaces, and different decentralisation properties — but the goal is the same: agreement on a single shared history, without anyone in charge.
Public vs private: not all chains are the same
The word blockchain gets used for a few different designs. The interesting one for crypto is the public blockchain — anyone can read, anyone can transact, anyone can run a node. Bitcoin and Ethereum are the canonical examples.
There are also permissioned chains, mostly used by enterprises, where a known group of operators run the nodes. These look a lot like databases with extra steps and are not what people usually mean by crypto.
Within public chains there is further variation. Some optimise for decentralisation and security (Bitcoin); some for performance and cost (Solana, modern L2s); some for programmability (Ethereum and the EVM family). The trade-offs are real and ongoing — the chain you pick for a use case actually matters.
What you can actually do with a blockchain
The headline use is sending money: a transaction moves a balance from one address to another and the network records it. But once you have a programmable chain, smart contracts open the door to much more.
A smart contract is a small program that lives on the chain and runs when called. It can hold balances, enforce conditions, and react to inputs. From this single primitive you get most of what modern crypto does: token swaps in DeFi, lending protocols, on-chain games, NFTs, DAOs, prediction markets, stablecoins.
None of it is magic. Everything a smart contract does is publicly verifiable code running on the same shared ledger. That is the property that makes blockchains interesting: not that they are fast or cheap (often they are neither), but that they let strangers transact without a trusted intermediary.
What blockchains are not good at
An honest guide has to include this. Blockchains are powerful for a narrow class of problems and a poor fit for most everything else.
They are slow compared to a centralised database. Even fast chains process thousands of transactions per second; a payments processor does hundreds of thousands.
They are public by default. Putting personal data on a public chain is almost always a bad idea — you cannot delete it, and pseudonymous addresses can be linked to identities over time.
They are expensive when busy. Block space is limited; popular activity pushes fees up. This is also why hype cycles correlate with painful transaction costs.
And they require trust in the code. A bug in a smart contract is permanent damage to anyone who depended on it; there is no customer support to call. This is real risk and the reason audits and time-on-the-clock matter more than slick UI.
Tracking the news that moves the chains
Blockchains evolve fast. Protocol upgrades change fee dynamics, validator dynamics, throughput. A new L2 redirects activity. A high-profile bug shifts confidence. Regulatory news shapes which addresses exchanges will touch. Following the wrong feeds means reacting late or to the wrong things. Zippfeed surfaces blockchain headlines with a sentiment score (bullish, neutral or bearish) and an importance rating, so you can tell a real upgrade from a marketing announcement and a real exploit from a Twitter rumour. This is education, not financial advice — but knowing what is actually changing under the hood is the difference between using a blockchain and just owning a ticker.
