1.14 Bitcoin Transactions

1.14 Bitcoin Transactions

A Bitcoin transaction is a signed instruction that changes which unspent transaction outputs can be spent. The network validates the transaction against protocol rules before miners include it in a block. This lesson follows a transaction from creation to confirmation.

Learning objectives

• Inputs and outputs
• Change outputs
• Digital signatures
• Transaction fees
• Mempool
• Block inclusion
• Confirmations

Why this matters

Bitcoin transactions do not work like a bank balance being debited. Understanding the actual input/output mechanism now will make wallet fees, "change" addresses and transaction explorers make sense instead of feeling arbitrary.

Core teaching

A Bitcoin transaction consumes one or more unspent transaction outputs (UTXOs) as inputs and creates one or more new outputs. Unlike a bank account, there is no running balance to simply decrement — if you want to send 0.02 BTC from a 0.05 BTC UTXO, the transaction must consume the entire 0.05 BTC input and create two new outputs: 0.02 BTC to the recipient, and roughly 0.0299 BTC (0.05 minus the recipient's amount minus a small fee) sent back to an address you control as change.

This UTXO model, rather than an account-balance model, is a deliberate design choice with real consequences: it affects wallet privacy (address reuse can link transactions together), how fees are calculated (based on transaction size, not amount sent), and how wallets track your spendable balance (as a set of discrete UTXOs, not one number).

Worked example

Suppose you control one unspent output worth 0.05 BTC and want to send 0.02 BTC to someone. Bitcoin transactions do not support partial spending of an output the way cash allows giving change from a note — instead, the transaction consumes the entire 0.05 BTC input and creates two new outputs: 0.02 BTC to the recipient and roughly 0.0299 BTC (minus a small transaction fee) back to an address you control, functioning as change.

This UTXO-based structure, rather than an account-balance model, is a specific design choice with consequences for privacy, wallet software complexity, and how fees are calculated — it is worth understanding as a mechanism, not just accepting that "transactions get confirmed".

Deeper analysis

A Bitcoin transaction is a structured instruction that spends previous outputs and creates new outputs. This model is important because it explains why a wallet balance is not a single number stored at one address. A transaction may combine several inputs, create multiple outputs and return change. Fees are associated with the transaction’s resource usage rather than simply with the monetary amount being sent.

Once broadcast, a transaction can be relayed by nodes and held in a mempool before being selected for a block. Inclusion in a block gives the transaction historical depth. Later blocks increase that depth, which generally increases the work required to replace the relevant history. A blockchain explorer makes these stages visible, but students should remember that explorer labels are interpretations layered on top of raw protocol data.

Common misconceptions

• A transaction can have multiple inputs and outputs.
• The fee is generally inferred from the difference between inputs and outputs.
• One confirmation is not the same as an absolute guarantee against every theoretical reorganisation.

Application lab

Using a blockchain explorer, look up any real Bitcoin transaction and identify its inputs and outputs. See if you can spot which output looks like the "payment" and which looks like "change" returned to the sender, based on the amounts.

Practical exercise

Write two sentences explaining, in your own words, why a Bitcoin transaction needs to consume a whole input and create a change output, rather than simply subtracting an amount from a running balance the way a bank account does.

Knowledge check

Question: Why does sending 0.02 BTC from a wallet holding one 0.05 BTC UTXO require creating a "change" output, rather than simply reducing a balance by 0.02?

Model answer: Bitcoin transactions consume entire UTXOs as inputs; they cannot partially spend one. To send less than the full input amount, the transaction must create a new output returning the remainder (minus the fee) to an address the sender controls.

Case study prompt

Use a blockchain explorer to look up any real Bitcoin transaction. Identify its inputs and outputs, and try to determine which output is the intended payment and which is change returned to the sender, based on the amounts.

Key takeaways

• Bitcoin transactions consume whole UTXOs, not partial balances
• Change outputs exist because inputs cannot be partially spent
• Fees are based on transaction size, not the amount transferred
• The UTXO model has real privacy and wallet-design consequences

Further exploration

Lesson 1.15 zooms out from individual transactions to the aggregate: how many BTC can ever exist, and what actually enforces that limit.