Bitcoin Transactions, Inputs, Outputs, and Public Traceability

Summary

This explainer describes how Bitcoin wallets create key pairs and addresses, and how transactions transfer value by referring to earlier transaction outputs. It walks through transaction fields such as identifiers, inputs, outputs, lock time, signatures, and script conditions. Multiple inputs can combine previously received outputs, while multiple outputs allow payment and change; any input value left after outputs becomes a fee for the miner who includes the transaction.

The article frames Bitcoin as a public ledger of linked transactions rather than separate serialized coins. It describes the genesis transaction and coinbase rewards, and notes that transaction signatures do not cover all data, leaving some fields malleable. It also argues that public transaction histories make Bitcoin pseudonymous rather than truly anonymous. This is an introductory conceptual account, not a protocol specification: it omits important details including Merkle trees, network operation, and the full script system, and its historical claims about future identification are speculative.

Key ideas

• Bitcoin inputs spend outputs from earlier transactions, linking value through the ledger.
• A transaction may combine multiple inputs and create multiple outputs, including an output for change.
• The difference between total inputs and outputs can be paid as a transaction fee.
• Public transaction records support tracing, so addresses provide pseudonymity rather than guaranteed anonymity.
• The article is an overview and omits protocol and network details.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.