How Does a Bitcoin Transaction Actually Work?

The problem the design solves

Digital money has an obvious flaw: files can be copied. If a coin is just data, what stops someone from spending the same coin twice? This is the double-spending problem, and the Bitcoin whitepaper presents its entire design as an answer to it — a way to prevent double-spending without a trusted central party like a bank checking every payment.

In short: the hard part of digital cash was never sending value; it was proving you didn't send the same value twice.

Step one: the signature

The whitepaper defines a coin as a chain of digital signatures. When an owner pays someone, they sign a message that says, in effect: "I transfer this coin, which I received in transaction X, to the holder of public key Y."

• The private key creates the signature. Only the owner holds it.
• The public key lets anyone verify the signature is genuine.
• Each transaction points back at the transaction where the coin was previously received, forming a traceable history.

Anyone can verify the whole chain of ownership. What they cannot verify from signatures alone is whether the owner already spent that coin somewhere else. (For more on keys, see keys, addresses, and wallets.)

Step two: the broadcast

The signed transaction is announced to the network — thousands of independent computers, called nodes, each keeping a copy of the ledger. There is no central switchboard; transactions spread from node to node.

Step three: mining and the timestamp

Here is where double-spending dies. Specialized nodes called miners gather broadcast transactions into candidate blocks and compete to solve a computational puzzle — proof of work. The winner's block is appended to the chain, and the network moves on to the next round.

The effect, as the whitepaper describes it, is a public timestamp: the network agrees on the order in which transactions happened. If someone signs two conflicting payments spending the same coin, only the one that makes it into the agreed chain first counts; nodes reject the other as invalid. NIST IR 8202 covers the same machinery from an engineer's viewpoint — hash-linked blocks, distributed consensus, tamper evidence.

In short: mining isn't really about creating coins; it's about getting a decentralized network to agree on what happened first.

Step four: confirmations

A transaction in the latest block has one confirmation. Each new block built on top adds another. The deeper a transaction is buried, the more work an attacker would need to redo to rewrite it — which is why recipients often wait for multiple confirmations before treating a payment as settled.

What this means in practice

• Finality is probabilistic, not instant. Settlement hardens as blocks accumulate.
• The ledger is public. Transactions are visible to anyone; identities are represented by keys rather than names.
• There is no undo button. The same design that prevents tampering also means no administrator can reverse a payment — a property with real consequences, discussed in the scam pattern glossary.

Bottom line

A Bitcoin transaction is a signed transfer, broadcast to a network, ordered by proof of work, and hardened by the blocks stacked on top of it. Every step exists to answer one question without a referee: which spend came first?