How does Bitcoin work? Blocks, UTXOs and mining in plain English

Strip away the noise and Bitcoin is a surprisingly simple machine: a public database, copied across thousands of computers, updated every ten minutes by whoever wins an open guessing competition. Still, a lot happens the moment you press send. So how does Bitcoin work, exactly? This guide walks through the machinery: what a transaction really contains, how blocks chain together, what miners do with all that electricity, and why nobody can spend the same coin twice. I wrote explainers like this for a living at Binance Academy, and one lesson stuck: a single worked example beats a page of theory. So we will follow one payment, Alice sending Bob 2 bitcoin, from her wallet to permanent settlement on the chain.

How does Bitcoin work in simple terms?

Bitcoin is a shared ledger of who owns what, stored on thousands of independent computers around the world. Users broadcast signed payment instructions, and roughly every ten minutes a miner bundles the latest ones into a block, proves it did costly computational work, and appends that block to the chain. Every computer then updates its copy.

The comparison I always reach for is your bank. A bank also runs a database of names and balances, and when you pay someone it simply edits two rows. The difference is that the bank's database is private and controlled by one company you have to trust. Bitcoin's is public, copied to anyone who wants it, and controlled by no single party.

The design came from a nine-page whitepaper published in October 2008 by the pseudonymous Satoshi Nakamoto. The network itself began producing blocks in January 2009 and has not stopped since.

Three roles keep it running. Users, like Alice, create and sign transactions. Nodes, ordinary computers running free software such as Bitcoin Core, store the full ledger and check every rule on every transaction and block. Miners compete for the right to write the next update. Alice's payment to Bob is about to pass through all three.

What is actually inside a bitcoin transaction?

Not account balances. A bitcoin transaction spends one or more unspent transaction outputs, or UTXOs, which work like receipts from earlier payments, and it creates new ones. Each input is a receipt handed over in full; each output is a fresh receipt assigning value to an address, usually including change back to the sender.

Here is the slightly awkward truth: there is no object in the system called "a bitcoin". No coin file, no token, no row that reads Alice: 5. The ledger is a long list of UTXOs, each recording an amount and the address it is locked to. Your balance is whatever your keys can unlock, added up.

Watch it work. Alice holds a single UTXO worth 5 bitcoin, change from an earlier transaction. To pay Bob 2, her wallet builds a transaction that consumes the whole 5-bitcoin receipt as its input and creates two outputs: 2 bitcoin locked to Bob's address, and 2.9999 bitcoin locked to a fresh change address of Alice's own. Nothing in the transaction says "fee". The 0.0001 gap between input and outputs simply becomes the miner's to keep.

UTXOs merge as easily as they split. Say Bob later receives 1 bitcoin each from three other people. His wallet now controls four receipts: one for 2 and three for 1. To spend 4.5, it would feed all four in as inputs and take the remainder, less a fee, back as change. An on-chain balance is really a purse of differently sized pieces, and wallet software quietly chooses which pieces to spend. The precise rules are set out in the Bitcoin developer guide.

How do public and private keys work in practice?

A private key is a secret number that produces unforgeable digital signatures; the matching public key lets anyone verify them. Addresses are derived from public keys, and every UTXO is locked to an address. To spend one, you must supply a valid signature, so owning bitcoin simply means controlling the right private keys.

When Alice's wallet assembles her transaction, it signs it with her private key. That signature proves two things to every node that sees it: the spender controls the key behind the address the 5-bitcoin UTXO was locked to, and the transaction has not been altered since signing. Verification uses only her public key. The private key never leaves her device.

Receiving is even simpler. Bob shares an address and waits; no signature and no online presence are needed on his side. Once the transaction confirms, a 2-bitcoin UTXO sits locked to his address, and only his private key can move it on.

This is why security in Bitcoin is really a key-management question. Coins never leave the ledger; what you hold is the power to reassign them, and if a private key is lost, its coins remain visible on the chain but unspendable forever. A bitcoin wallet is best understood as a keychain and signing tool, not a container of coins.

How does the blockchain actually chain blocks together?

Every block carries a cryptographic hash of the block before it: a small fingerprint of that block's entire contents. Change one character in an old block and its fingerprint changes, breaking every later block's reference. That linkage is the chain, and it makes settled history tamper-evident all the way back to 2009.

A hash function such as SHA-256 takes any input and returns a fixed-length fingerprint. The same input always gives the same output, and the tiniest change produces an unrecognisably different one. Suppose Alice's payment confirms in a block we will call block N. Block N+1 embeds N's hash in its header, N+2 embeds N+1's, and so on. Anyone hoping to alter her transaction later would have to rebuild block N and every block after it, and as the next section shows, rebuilding blocks is deliberately, ruinously expensive.

Blocks are also kept small on purpose. The base limit is 1 MB, stretching to roughly 4 MB of block weight since the SegWit upgrade, and a new block arrives only about every ten minutes. Both figures are compromises. Ten minutes gives every node on Earth, including those on slow connections, time to receive, validate and store each block before the next lands. Modest blocks keep the full chain, now hundreds of gigabytes covering every transaction since 2009, small enough for a hobbyist's hard drive. Bigger, faster blocks would add capacity, but the ledger would swell until only datacentres could hold a copy and the network would drift out of sync more often. Disagreement over precisely this trade-off produced some of the most famous forks in Bitcoin's history.

What do bitcoin miners actually do?

Miners gather pending transactions from the mempool, assemble them into a candidate block, then hash the block header over and over while varying a number called the nonce. They are hunting a hash below the network's current target, and the first to find one broadcasts the block and collects new bitcoin plus fees.

There is no skill in the search. Finding a qualifying hash is a lottery in which each guess is a ticket, and the network as a whole makes quintillions of guesses every second. That is the "work" in proof of work: a winning hash takes an astronomical number of attempts to find but a microsecond for everyone else to verify, so a valid block is self-evident proof that serious electricity was spent producing it.

A difficulty dial keeps the pace steady. Every 2,016 blocks, roughly two weeks, the protocol compares actual block production against the ten-minute target and retunes how hard the puzzle is. Mining hardware has gone from Satoshi's ordinary CPU to warehouses of purpose-built chips, yet blocks still arrive about every ten minutes, because the target simply becomes harder to hit.

Alice's transaction meets the miners in the mempool, the shared waiting room for unconfirmed payments. Block space is scarce, so miners fill their candidate blocks with the highest fee rates first. Alice attached a mid-range fee: on a quiet day she confirms in the next block or two, on a busy day she waits longer or bumps the fee. You can watch this queue, and every block that clears it, live at mempool.space.

Most miners do not gamble alone. The odds of one small machine winning a block are so long that miners pool their guessing power and split rewards in proportion to the work each contributed. And cheating does not pay: a block containing an invalid transaction is rejected by every node regardless of the work behind it, so a dishonest miner pays the full power bill and earns nothing. The full mechanics are covered in the mining section of the developer guide.

How did Bitcoin solve the double-spending problem?

Digital things are trivially copyable, so every earlier digital cash scheme needed a central bookkeeper to stop the same money being spent twice. Bitcoin replaces that referee with thousands of nodes enforcing identical rules, plus a tie-breaker: when two valid versions of history compete, the one with the most accumulated proof of work wins.

Send a friend a photo and the original stays on your phone. If money worked like that it would be worthless, and this, not encryption or scarcity, was the problem that sank digital cash for decades. Satoshi's whitepaper frames Bitcoin's entire design as the answer: peer-to-peer electronic cash with no trusted party in the middle.

The UTXO model does half the job. Alice's 5-bitcoin receipt can be spent exactly once; the moment her payment to Bob confirms, that UTXO leaves the unspent set on every node's copy of the ledger. If she signed a second transaction spending the same UTXO elsewhere, honest nodes would reject whichever arrived second, and at best the two would race for a single slot. One confirms, the other becomes waste paper.

Proof of work does the other half. Occasionally two miners find valid blocks almost simultaneously and the network briefly sees two competing tips. Nobody votes and nobody adjudicates. The next block simply lands on one side, and every node follows the chain with the most work behind it. The losing block is orphaned and its miner forfeits the reward, which is why miners abandon stragglers quickly and return to the main chain. This rule is known as Nakamoto consensus.

It is also why recipients wait for confirmations. Each block stacked on top of the one containing Bob's payment is another block an attacker would need to out-mine, from behind, against the combined power of the whole network. After three to six confirmations, roughly thirty to sixty minutes, reversal is a practical impossibility, which is exactly why exchanges credit deposits only after a handful of blocks.

Nothing in this design trusts anyone. Every node checks every signature, every amount and every coinbase payout in every block, and quietly drops whatever fails. Honesty is not assumed in Bitcoin; it is simply the only strategy that pays.

How do the 21 million cap and the halving actually work?

New bitcoin are created in only one place: the first transaction of each block, called the coinbase, which pays the winning miner. That subsidy began at 50 bitcoin per block and halves every 210,000 blocks, roughly every four years. It stands at 3.125 bitcoin today, and the schedule runs out around 2140, just short of 21 million coins.

The coinbase transaction is unusual in that it has no inputs. It mints the block subsidy from nothing, adds every fee paid in that block, and locks the total to the miner's address. (The exchange named itself after the transaction type, not the other way round.) The miner who confirmed Alice's payment collected 3.125 newly minted bitcoin plus all the block's fees, her 0.0001 included.

The halving schedule so far: 50 became 25 in 2012, then 12.5 in 2016, 6.25 in 2020 and 3.125 at the April 2024 halving. The next, expected in 2028, cuts it to 1.5625. Because the timetable is written into the protocol, total supply at any future date can be calculated to the coin, something true of no commodity and no national currency. More than 19 million of the eventual 21 million bitcoin are already in circulation, and the remainder trickles out ever more slowly for the next century. You can see the full halving schedule and live network figures in one place.

The cap is not a promise anyone keeps; it is arithmetic everyone checks. A block whose coinbase pays even one satoshi more than the schedule allows is invalid on every node, whatever work went into it. Changing that would mean persuading essentially the whole network, node operators, miners and users alike, to voluntarily run software that inflates away their own holdings. This predictable, hard-capped issuance is why Bitcoin gets called digital gold, with one difference: nobody knows exactly how much gold is left in the ground, while Bitcoin's remaining issuance is known to the decimal place.

The fading subsidy is also the long-term security plan. As each halving trims the coinbase, transaction fees like Alice's are designed to take over, gradually, as the income that keeps miners securing the chain.

Frequently asked questions

How long does a bitcoin transaction take to confirm?

One confirmation takes about ten minutes on average, though individual blocks can arrive within seconds of each other or be an hour apart. Wallets and exchanges commonly wait for three to six confirmations before treating a payment as final, so allow up to an hour for meaningful sums. Higher fees buy earlier inclusion.

Who controls the Bitcoin network?

Nobody, and everybody. Rule changes only stick if thousands of independent node operators choose to run software that adopts them. Miners order transactions but cannot rewrite the rules: a block that violates consensus is rejected regardless of the work behind it. Serious disagreements have historically ended in forks rather than takeovers.

Can the 21 million cap ever be changed?

In theory, yes: the code is open source and anyone can propose anything. In practice, raising the cap would require nearly every node operator, miner and holder to voluntarily adopt software that devalues their own coins. Meanwhile, any block that overpays its miner today is simply rejected by the entire network as invalid.

What happens when all 21 million bitcoin are mined?

The final fraction of a bitcoin arrives around 2140, so nobody reading this will see it. Long before then, transaction fees are designed to replace the shrinking block subsidy as miners' main income. The shift is gradual by construction: every halving trims the subsidy, and fees carry a little more of the load each cycle.

Do I need to understand UTXOs to use Bitcoin?

No. Wallet software selects which pieces to spend, calculates change and sets fees without showing you any of it. Understanding the model is still worthwhile: it explains why your balance is really a collection of differently sized pieces, why fees depend on a transaction's data size rather than its value, and what consolidating means.