One-sentence answer

Nodes independently check whether the funds referenced by a transaction have already been used and accept only a rule-valid spend that becomes part of valid history.

Copying information is not copying ownership

A photo can be copied because simultaneous copies do not conflict. Payments are different: if the same funds are assigned to two people, the system must determine which ownership change counts.

Bitcoin does not stop messages from being copied. It lets every node detect transactions that conflict.

Nodes check; blocks order

A transaction references earlier unspent outputs. Nodes verify signatures and rules, but may briefly see two conflicting transactions. Miners include one in a candidate block, and later blocks accumulate work on a valid chain.

Replacing that established history requires redoing a growing amount of work, so it becomes progressively harder.

A confirmation is not a magic switch

Zero confirmations means a transaction has propagated but is not yet in a block. One confirmation means it is in a valid block. More confirmations mean more work has accumulated after it—not that a central approver clicked a button.

Three things to remember

  1. Messages can be copied; the same funds cannot be used twice in valid history.
  2. Nodes detect conflicts and proof of work helps order history.
  3. Confirmations describe how much subsequent work reinforces a transaction.

A common follow-up

Does seeing a transaction mean payment is final?

Not necessarily. It may have propagated without entering a block. The appropriate confirmation threshold depends on the situation and risk.

Primary sources

Primary sources

These links lead to protocol material, developer documentation, or open-source code—not trading services.

  1. Bitcoin: A Peer-to-Peer Electronic Cash SystemSatoshi Nakamoto
  2. Transactions — Developer GuideBitcoin.org