How Does Bitcoin Work? | The Parts You Must Understand

Bitcoin records payments on a shared ledger, groups them into blocks, and secures the chain with cryptography so rewrites get expensive.

Bitcoin can feel like a trick the first time you send it. You tap “send,” a few minutes pass, and the payment shows up on the other side without a bank pushing it through. In the middle is a stack of plain ideas: signatures prove you’re allowed to spend, the ledger shows what is already spent, and a network agrees on one history of transactions.

This article walks through those ideas in order, then zooms in on the bits that change real outcomes, like fees, confirmation time, and what a wallet is doing when it “signs.” By the end, you’ll be able to read a block lookup page with less guesswork and pick safer habits when you hold or move bitcoin.

How Does Bitcoin Work? A Plain-English Walkthrough

Start with one problem: stopping double-spends. Digital files can be copied, so a digital coin needs rules that stop one person from paying two people with the same coins. Bitcoin solves that by keeping a public record of spends, then making it hard to rewrite that record after the fact.

Bitcoin is best understood as entries in a ledger, not files that slide from device to device. When you “own” bitcoin, you control a secret number that lets you create a valid signature for spending certain past outputs. The network checks that signature, checks that the coins were not spent already, and then accepts the new transaction into the shared history.

• You create a transaction that points to spendable outputs and names new recipients.
• Your wallet signs the transaction with your secret spending number.
• You broadcast it to the network through a node (yours or someone else’s).
• Nodes verify it and relay it to peers.
• Miners gather valid transactions into a block and compete to add that block to the chain.
• Once a block is accepted, your transaction gains confirmations as new blocks stack on top.

What A Wallet Actually Holds

A wallet does not hold coins. It holds the secrets that let you spend coins recorded on the ledger. The “coins” your wallet spends are unspent transaction outputs (often shortened to UTXOs). A UTXO is a chunk of value created by a past transaction that has not been spent yet.

When you pay someone, the wallet selects one or more UTXOs, spends them as inputs, and creates new outputs. One output goes to the recipient. Another often returns change to you, because UTXOs get spent whole, a bit like handing over a banknote and receiving change back.

Wallets come in two broad styles:

• Custodial: a service controls the spending secrets. You log in and see a balance.
• Non-custodial: you control the spending secrets. Your recovery phrase is the backup, so losing it can mean losing access.

Non-custodial does not require running your own node, though running one can reduce data leaks. Many wallets connect to public servers. Others can connect to your own node, trading setup time for stronger privacy.

Signatures, Hashing, And Why The Ledger Can Be Trusted

Bitcoin uses public/private cryptography. You keep a private secret. You share a public identifier derived from it. A signature proves that whoever signed held the private secret, without revealing it.

When you spend, you sign a transaction that references specific previous outputs. Nodes verify the signature against the public data tied to those outputs. If the signature is valid and the output is still unspent, that part of validation passes.

Hashing is the other pillar. Hash functions turn data into a fixed-length digest. The same input gives the same digest. Tiny changes give a different digest. This property lets the system link blocks, build Merkle trees, and run proof-of-work. NIST’s Secure Hash Standard is a solid reference for how SHA-256 and related hashes work in computing. FIPS 180-4, Secure Hash Standard (SHS) gives the formal definition.

Nodes, Mempools, And Shared Rules

A Bitcoin node is software that validates blocks and transactions. It keeps its own copy of the chain and enforces consensus rules. Those rules cover things like valid signatures, block size limits, and the schedule for new coin issuance.

When a node receives a new transaction, it runs checks. If it passes, the node holds it in a waiting area called the mempool, then relays it. If it fails, it gets dropped.

Miners do not get to bend the rules. They can choose which valid transactions to include, yet the blocks they publish still must pass every validation rule or nodes reject them.

If you want to see how inputs, outputs, and scripts fit together, the Bitcoin developer documentation has a clear breakdown. Transactions — Bitcoin maps cleanly to what you see on a block lookup page.

How Bitcoin Works With Blocks And Mining

Why do we need blocks and mining? The network needs one history, and it needs a way to pick that history without a central referee.

Mining is a competition. Miners gather transactions from mempools into a candidate block. Then they search for a nonce that makes the block header hash meet a difficulty target. That search takes energy and time, which makes creating blocks costly.

When a miner finds a valid block, it broadcasts it. Nodes verify the block and, if valid, add it to their chain tip. Short-lived forks can happen when two miners find blocks near the same time. Nodes follow the chain with the most accumulated work.

The original paper that introduced this design explains the double-spend problem, the proof-of-work chain, and the incentive model. Bitcoin: A Peer-to-Peer Electronic Cash System is still the cleanest starting point for the “why.”

Confirmations And Settlement Risk

A confirmation is a count of how many blocks have been built on top of the block that includes your transaction. One confirmation means your transaction is in the latest block. Six confirmations means five more blocks were added after it.

Each added block raises the cost to rewrite history, because an attacker would need to redo proof-of-work and then catch up to the honest chain. For small payments, some merchants accept zero confirmations with extra caution. For larger payments, waiting for multiple confirmations is standard practice.

Fees: What You Pay For Block Space

Bitcoin fees go to miners. Fees are not based on the amount sent. They are mostly tied to transaction size in bytes and to demand for block space.

Wallets estimate fees by watching recent blocks and mempool conditions. Many wallets let you choose a slow, medium, or fast setting. Under the hood, that choice sets a fee rate, often quoted as satoshis per virtual byte (sat/vB).

Fees also shape how you build transactions. Many small inputs can make a transaction large, which can raise the fee. Consolidating UTXOs when fees are low can reduce later costs, though it can also link addresses and reduce privacy.

Table: Core Parts And What Each One Does

This table names the moving parts you’ll see again and again.

Part	What It Is	What It Does
Private secret	A random 256-bit number kept secret	Lets you create valid spending signatures
Public identifier / address	Shareable data derived from the private secret	Gives others a destination for payments
UTXO	An unspent output from a past transaction	Acts as the value your wallet spends as an input
Transaction	Inputs, outputs, and signatures	Spends old outputs into new ones
Mempool	A node’s waiting set of valid unconfirmed transactions	Feeds miners candidates for blocks
Block	A batch of transactions plus a header	Anchors transactions into shared history
Merkle tree	A hash tree over transactions in a block	Proves inclusion without sending the full block
Node	Validation software that relays data	Enforces consensus rules and keeps a chain copy
Miner	A node that also performs proof-of-work	Competes to add new blocks and earns fees plus subsidy
Difficulty target	A threshold for acceptable block header hashes	Keeps block timing near a set pace

Layer Two And Faster Payments

On-chain transactions are global and auditable, yet block space is limited. Layer-two systems move many small payments off-chain while still leaning on the base chain for enforcement.

The most known layer-two system is the Lightning Network. It uses payment channels: two parties lock funds on-chain, then exchange signed updates that change who can claim the funds. Only the open and close hit the chain in the normal case. Routing lets you pay someone you do not have a direct channel with, as long as there’s a path of channels between you.

The protocol details for Lightning are specified in the BOLT documents. BOLT: Basis of Lightning Technology is where message formats and channel rules are written down.

Table: Common Ways People Send Bitcoin And The Trade-offs

“Sending bitcoin” can mean a few different rails. Picking the right one depends on size, speed, fees, and who holds the spending secrets.

Method	Best Fit	What To Watch
On-chain transaction	Larger payments, settlement, storage moves	Fees can spike; wait for confirmations for higher-risk transfers
Lightning payment	Smaller payments, frequent spends	Channel balance can limit receive capacity
Custodial transfer inside an app	Fast internal sends between users of one service	You rely on the service for access and solvency
Batch payout	Services paying many recipients at once	Recipient timing depends on when the batch is broadcast
Fee bump with RBF	Unconfirmed payment stuck with a low fee	Works only if the original transaction signaled RBF

Practical Safety Habits That Pay Off

• Back up your recovery phrase offline. Treat it like a master secret. Store it where water and fire are less likely to destroy it.
• Use a hardware wallet for larger holdings. It keeps spending secrets off internet-connected devices and reduces exposure to malware.
• Confirm addresses on a trusted screen. Clipboard malware swaps addresses. A hardware wallet display helps you catch that.
• Send a small test amount when stakes are high. It’s a cheap way to confirm you copied the right destination.
• Be cautious with QR codes from strangers. A printed code can be swapped. Verify the address text too.

Putting It Together

Bitcoin works because it turns ownership into control of spending secrets, turns spending into signed messages, and turns agreement into a public chain of proof-of-work blocks. Nodes verify everything cheaply. Rewriting history costs real resources. That combo lets strangers transact without a central operator deciding which payments count.