How a Block Stops the Same Crypto Being Spent Twice

Since Bitcoin's genesis block was mined on Jan. 3, 2009, blocks have prevented double spending by ordering valid transactions and forcing every node to reject value already spent. That replaced a bank's private ledger with a history anyone running the software can check. Ethereum's Merge on Sept. 15, 2022 changed the resource used to select block producers—from computing power to staked ether—but preserved the core defense: one accepted state, independently verified.

How does a block reject a double spend?

A block does not search for counterfeit coins; each node tests proposed transactions against its current ledger state before accepting the block. In Bitcoin, a transaction consumes specific unspent transaction outputs. The signature must authorize that spend, and the same output cannot be consumed again. If two transactions name one output, only the first in the accepted history can pass.

Ethereum applies the same principle to accounts. A transaction needs sufficient balance and the sender's next nonce, a sequential number. Two transfers carrying the same nonce cannot both execute. A validator may choose which conflict to include, often favoring the transaction with the better fee, but other nodes recompute the block and reject it if the resulting state breaks protocol rules.

• Mempool: conflicting transactions can circulate because neither is settled.
• Block: the producer proposes one order; peers verify every state change.
• Chain: consensus selects the history that later blocks or finality support.

What happens when two valid blocks conflict?

Consensus decides which history survives when two individually valid blocks compete at the same height. Bitcoin nodes follow the valid chain with the most accumulated proof of work. Ethereum combines a proof-of-stake fork-choice rule with finality votes. A transaction in a discarded branch can return to the pending pool, which is why one block is not an absolute guarantee.

More confirmations make a Bitcoin reversal progressively harder because an attacker must catch and overtake continuing work. Ethereum's finalized checkpoints impose a different barrier: conflicting finality requires validators to violate rules and risk losing stake. Neither model makes reorganization metaphysically impossible; each makes it observable and costly under stated assumptions about honest control of the scarce resource.

Who pays to prevent double spending?

Users pay transaction fees, while miners or validators supply the ordering service and earn protocol rewards plus fees. Proof-of-work miners bear hardware and electricity costs. Proof-of-stake validators lock capital and accept slashing risk. Holders and applications benefit from a ledger whose state does not depend on one operator.

A conventional payment database can also stop duplicate spends, usually faster and more cheaply, but its owner alone controls ordering, reversals and access. A public blockchain buys independent verification and censorship resistance at the price of duplicated computation, delayed settlement and fee competition. That trade is worthwhile only when shared control matters.

Where can double spending still happen?

Blockchain rules prevent duplicate use of native on-chain state; they do not prevent an intermediary from issuing duplicate promises against one asset. The distinction is central to the uAsset bridge design: a wrapped balance can be a claim on backing held elsewhere, so solvency and redemption depend on custody as well as consensus.

The verdict is narrower and stronger than “blockchains make fraud impossible.” On a correctly validating network, two conflicting spends cannot both remain in the accepted ledger. Reorganizations, majority attacks, software bugs and off-chain liabilities remain possible, but blocks turn transaction ordering from a private assertion into a reproducible test backed by an economic cost.