How blockchain works: Transactions, blocks and consensus
Follow a crypto transaction from wallet signature to confirmation and see how hashes and consensus keep a shared ledger in sync.
In this guide · 9 sections
- The problem blockchains were designed to solve
- A ledger with no single owner
- Blocks, linked by hashes
- What a hash function actually does
- Public and private keys: how ownership is proven
- How the network agrees on what’s true
- What happens when two nodes disagree
- Read a transaction without confusing the stages
- Why this design matters practically
From signed message to credited balance
The blockchain records a transfer; the receiving service decides when to show it as spendable.
- 1 · SignYour wallet authorizes a transaction. Check address, network, asset and amount.
- 2 · BroadcastNodes see a pending transaction. A transaction ID is not yet a confirmation.
- 3 · IncludeA miner or validator places a valid transaction in a block under that chain's rules.
- 4 · CreditAfter sufficient confirmation or finality, the receiver applies its own deposit policy.
A blockchain is often described as a database, which is technically true and not very illuminating. What actually distinguishes a public blockchain from a normal company database is who can check the copy, how updates are accepted, and what it takes to replace the past. The transaction path above is the fastest way to see the difference.
The problem blockchains were designed to solve
Digital money needs a way to prevent double-spending: the same balance cannot pay two recipients. A bank solves this with its own ledger. Bitcoin’s approach uses a shared ledger and rules for agreeing which transactions enter it, so no single bank has to maintain the authoritative copy. That changes the trust model; it does not eliminate fraud, software risk or mistakes by users.
Imagine Alice broadcasts two conflicting transactions spending the same bitcoin output. Nodes can observe both, but the network’s rules cannot accept both as valid spends in the same history. A miner may include one in a block; the other then conflicts with an already spent output. The point of consensus is not to decide whether Alice’s purchase was wise. It is to decide which valid transaction history the network follows.
A ledger with no single owner
A public blockchain is a transaction record maintained across a network rather than by one company’s database. Full nodes verify the rules and retain the data needed to check history; lighter clients may rely on other nodes for some information. A transaction is broadcast, checked against the network’s rules and, if selected, included in a block. The exact roles differ between Bitcoin, Ethereum and other chains.
Not every system called a blockchain is open to everyone. A permissioned network can restrict who submits transactions, runs validators or reads data. That may fit a business workflow, but its trust model is not the same as Bitcoin’s open network. Ask who can validate, who can change the rules, and who can see the ledger before treating “blockchain” as a security claim.
Blocks, linked by hashes
Transactions are grouped into blocks, and a block header refers to the previous block’s hash. Changing earlier data breaks that link and is detectable. Hash links alone do not make a chain immutable: the network’s consensus rules and the cost of replacing accepted history matter as well. That is why users wait for confirmations or finality rather than treating a broadcast transaction as settled.
What a hash function actually does
A hash is a fixed-length fingerprint of data. The same input gives the same output; a small change produces a different output. A node can therefore detect an altered block by checking its hash and links. A hash does not by itself prove that the transaction was honest or that an external claim was true. It also does not encrypt the ledger: on many public chains, transaction details are visible even if an address is not a legal name.
Public and private keys: how ownership is proven
A wallet signs an outgoing transaction with a private key. Network participants can verify the signature without seeing that secret. An address can be shared to receive funds, but the private key or recovery phrase must remain private. Control of a key is not proof of legal ownership; it is the technical ability to authorize transactions. See our custody comparison for what changes when a platform holds the keys.
How the network agrees on what’s true
Consensus is the rule set for accepting a shared history. Bitcoin uses proof of work: miners expend computing power, and valid chains are compared by cumulative work. Ethereum uses proof of stake: validators put ETH at risk and participate in proposing and attesting to blocks. The security and finality details differ; “confirmed” does not mean exactly the same thing on every network.
What happens when two nodes disagree
Two valid blocks can temporarily compete at the chain tip. On Bitcoin, the branch with greater cumulative work wins under the consensus rules; a transaction in a displaced block may need inclusion again. Ethereum uses validator attestations and a separate finality mechanism. This is why a receiver may require several confirmations or a finalized state before crediting a deposit.
Read a transaction without confusing the stages
If a wallet or platform supplies a transaction ID, open an explorer for the correct chain and inspect the destination, amount, status, block and confirmation or finality information. Do not use a Bitcoin explorer to check an Ethereum transaction or assume a token ticker identifies its network. The explorer shows what the chain has recorded. It cannot tell you whether an exchange has finished its internal review or when a receiving account will make the funds available.
No transaction ID yet? The sender may have created an internal request without broadcasting it. A search on a block explorer will not diagnose that stage. Ask the sending service whether the transfer has been submitted to the network, and use its authenticated support route. If the chain shows success but the receiver shows nothing, compare the asset, network, destination and the receiver’s stated deposit requirements before contacting its verified support.
| Visible status | What it proves | What it does not prove |
|---|---|---|
| Request shown in an app | The service has recorded an instruction | That a blockchain transaction exists |
| Transaction ID found, pending | A transaction has reached at least part of the network | That it will be included or credited |
| Included in a block | The chain has recorded it at that point in history | That the receiver has released a usable balance |
| Confirmed or finalized | The chain’s settlement condition is stronger | That a wrong address or network can be reversed |
Why this design matters practically
The combination of independently checked rules and a shared history lets a public blockchain settle transfers without a bank maintaining the sole authoritative ledger. But the chain verifies protocol conditions, not off-chain promises. It cannot prove that a seller will deliver goods, that a token issuer has reserves or that a website is trustworthy.
A recipient may voluntarily send assets back, and some services may adjust their own account records, but users should not expect a credit-card-style chargeback of a settled on-chain transfer. That is why the address and network check matters before signing.