A blockchain records a transaction by letting many independent computers check it, bundle it with other transactions into a block, and chain that block to the previous one using a cryptographic fingerprint called a hash. Change one old entry and its fingerprint changes, which breaks every link after it, so a cheater would have to redo that work faster than the rest of the network or win over most of it.
That is the whole idea behind the word "immutable". It does not mean editing is physically impossible. It means editing is so expensive and so visible that, on a large network, nobody sensible tries. The rest of this guide walks through one transaction from the moment you press Send, in plain language.
What happens when you press Send?
Imagine you send a small amount of a digital asset to a friend. Your wallet app does not "move coins" the way a bank app seems to move money. It writes a short message that says, in effect: this address gives that address this amount, and here is a fee for whoever records it. Then it signs that message with your private key. The signature is a piece of math that anyone can check against your public address, but nobody can forge without the key.
The signed message is sent to a handful of computers on the network, called nodes. Each node checks two things before passing it on: is the signature valid, and does the sending address actually have enough to spend? If either check fails, the node drops the message. If both pass, the node forwards it to its neighbours, and within seconds the transaction has spread across thousands of machines that have never heard of you.
Valid transactions wait in a holding area, often called the mempool. Think of it as the queue at a post office counter. Whoever gets to write the next page of the ledger, a miner or a validator depending on the network, picks transactions from that queue. When the network is busy, they usually pick the ones offering higher fees first, which is why the same transfer can cost very different amounts on a quiet Sunday and during a market panic.
The chosen transactions are packed into a block. The block also contains the hash of the previous block, which is what makes it a chain. Once the block is accepted by the network, your transaction has one confirmation. Every new block stacked on top adds another. Exchanges and merchants usually wait for several confirmations before treating a payment as final, because the newest block is the one most likely to be replaced if two producers briefly disagree.
Notice what did not happen. No central server approved you. No one checked your name. And there is no "cancel" button once the transaction is in a block. That last point is the one that surprises people most, and it is the reason the rest of this category spends so much time on keys, addresses and scams.
Blockchain terms you will meet, in one line each
Hash. A fixed-length fingerprint of any data. Change one comma in the input and the fingerprint changes completely, so it is easy to spot tampering.
Block. A batch of transactions plus a header that includes the hash of the block before it. The header is what links the pages of the ledger together.
Node. A computer that keeps a copy of the ledger and checks the rules. Some nodes also produce blocks; many only verify.
Digital signature. Proof, created with a private key, that the owner of an address approved this exact message. It cannot be reused for a different message.
Mempool. The waiting area for valid transactions that are not yet in a block. Each node has its own view of it, so it is not one single list.
Consensus. The rule set that decides who writes the next block and which version of the chain everyone follows when there is a disagreement.
Confirmation. Each block added after the one containing your transaction. More confirmations mean it is harder to undo.
Fee. What you pay the block producer to include your transaction. It depends on network demand, not on how much value you are sending.
Finality. The point at which a transaction is treated as permanent. Some networks reach it after a fixed step; others only make reversal less and less likely over time.
Why can't anyone just edit the ledger?
Picture an old village savings group where every member keeps an identical notebook. Each evening, the treasurer reads out the day's entries, everyone writes them down, and at the bottom of the page they all copy a short code calculated from that page plus the code at the bottom of yesterday's page. If someone later rubs out an entry from last month, their notebook's codes stop matching from that page onwards. Everyone else can see at a glance which notebook has been altered.
A blockchain does the same thing with computers and much stronger math. The hash of each block depends on its contents and on the previous block's hash. Altering an old transaction means recalculating that block and every block after it, then getting the rest of the network to prefer your rewritten version over the one they already have.
How hard that is depends on the consensus method. On proof-of-work networks, producing a block requires burning real computing power, so rewriting history means out-computing everyone else combined. On proof-of-stake networks, block producers lock up the network's own asset as a deposit, and cheating can cost them that deposit. Both designs turn honesty into the cheapest option rather than relying on trust.
The honest caveat: small networks with few participants are far easier to attack than large ones, and there have been real cases of history being rewritten on small chains. So "blockchain" by itself is not a guarantee. The size, spread and incentives of the specific network matter.
Proof of work vs proof of stake: what actually differs?
The two most common consensus methods solve the same problem in different ways. Neither is "better" in every sense; they trade off different costs.
| Aspect | Proof of work | Proof of stake |
|---|---|---|
| Who writes blocks | Miners competing with computing power | Validators selected in proportion to locked deposits |
| What it costs to take part | Specialised hardware and electricity | Holding and locking the network's asset |
| What stops cheating | Rewriting history needs more computing power than the honest majority | Misbehaving validators can lose part of their deposit |
| Main criticism | High energy use | Influence can concentrate among large holders |
| When a transaction feels final | Gradually, as more blocks pile on top | Often at a defined checkpoint, depending on design |
Whichever method a network uses, the lesson for ordinary users is the same: wait for the confirmations your recipient asks for, and do not treat a transaction as done just because a wallet shows it as "sent".
What a blockchain does not guarantee
That the data is true. A blockchain faithfully stores whatever was submitted. If someone records a false claim, it is now a permanently stored false claim.
Who is behind an address. The chain knows keys, not people. A friendly name in a chat app is not proof that an address belongs to that person.
That mistakes can be undone. Send to the wrong address and there is usually no help desk that can reverse it. Only the receiver can send it back.
Privacy. Most public blockchains are transparent. Anyone can follow funds between addresses, and once one address is linked to your identity, much of your history can be traced.
Low fees. Fees float with demand. A transfer that costs very little on a quiet day can cost much more when the network is congested.
Speed. Some networks confirm in seconds, others take many minutes. Recipients may also wait for several confirmations before acting.
That a project is honest. A token running on a solid blockchain can still be launched by people who plan to disappear. The ledger is sound; the people may not be.
Legal clarity. Rules on digital assets differ by country and are still changing in Vietnam. Check current official guidance or ask a lawyer before relying on any assumption.
How to see this for yourself without spending money
You do not need to buy anything to watch a blockchain work. Every major public network has a block explorer, a website that shows blocks and transactions as they arrive. Search for a recent block and look at its parts: the list of transactions, the hash of the block, and the hash of the previous block that it points to. Seeing those two hashes side by side makes the "chain" idea click.
Many networks also run test networks, where the assets have no value and exist only for practice. Developers use them to try things safely, and learners can too. A test wallet lets you send, wait for confirmations and read your own transaction on an explorer without any money at risk.
One warning applies even here. Only use explorers and test tools you reached by typing a well-known address yourself, not via an ad or a link from a stranger. Fake explorers and fake "test" sites exist precisely to trick curious beginners into connecting a real wallet.
If you are learning for work, for example to judge whether a supplier's "blockchain-based" product is real, this hands-on look is worth more than any slide deck. You will quickly see what is stored on-chain and what is simply a normal database with a blockchain label attached.
Frequently asked questions
Can a blockchain transaction be reversed?
In normal use, no. Once a transaction is in a block and has enough confirmations, only the receiver can choose to send the funds back.
Why did my transaction stay "pending" for so long?
Usually the fee was too low for how busy the network was, so block producers kept picking other transactions first. Some wallets let you replace it with a higher fee; check your wallet's help pages.
Is blockchain the same as Bitcoin?
No. Bitcoin is one network that uses a blockchain. The same idea of a shared, hash-linked ledger is used by many other networks and by some private business systems.
Does a blockchain know my name?
The chain itself stores addresses, not names. But exchanges that verify identity, and any public post linking you to an address, can connect your identity to your on-chain history.
How many confirmations are enough?
It depends on the network and on how much is at stake; the recipient usually sets the number. For your own peace of mind, follow what the receiving service states rather than a rule of thumb from a forum.
