Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.31
EST. MONTHLY
205
DAYS
EST. ROI
A Bitcoin transaction spends one or more earlier unspent outputs and creates new outputs. The wallet selects funds, states the new spending conditions, calculates change and a fee, then produces the signatures required by the selected inputs.
The signed transaction is sent to nodes. They check it before relaying it, and a miner may later include it in a block. A wallet can display the payment before confirmation, but the network history changes only when an accepted block records it.
Estimated reading time: 7 minutes
TL;DR
- Inputs spend specific earlier outputs; outputs create new spendable amounts and conditions.
- A signature authorises the transaction without revealing the private key.
- Nodes validate and relay it, while miners decide whether and when to include it in a block.
What This Means in Simple English
A Bitcoin payment does not move a coin-shaped object between accounts. It uses earlier received chunks as inputs, proves permission to spend them and creates new chunks for the recipient and usually change back to the sender.
Simple Example
You pay a £7 bill with a £10 note. The whole note is used, the shop receives £7 and you receive £3 change. Bitcoin records the old output as spent and creates new outputs, with a small difference available as the miner fee.
Key Terms in Plain English
| Input: | A reference and proof spending an earlier output. |
|---|---|
| Output: | A new amount and spending condition. |
| TXID: | A transaction identifier calculated from transaction data. |
| Change: | Surplus value returned through a new wallet output. |
| Signature: | Cryptographic authorisation satisfying an input's conditions. |
The Parts of a Bitcoin Transaction
A transaction includes a version, inputs, outputs and a lock-time field, with witness data where relevant. Each input references a previous transaction identifier and output index.
Each output states a satoshi value and locking script. The structure can represent a simple payment, multiple recipients, a channel operation or more complex conditions.
How a Wallet Selects Inputs
A wallet may control many UTXOs. Coin-selection logic chooses enough value for the recipients and fee while considering size, privacy, labels and change.
Selecting many small inputs can increase the fee. Manual coin control can help experienced users, but careless selection can link history or leave an awkward remainder.
Why Change Is a New Output
Inputs are spent completely. If their value exceeds recipients plus fee, the wallet creates a change output to a new address it controls. Change is not a refund sent later; it is part of the same transaction.
Failing to create the intended change can turn the surplus into fee. Hardware-wallet screens and decoded transaction views should be checked for both recipient and change behaviour.
What the Signature Proves
The wallet signs data defined by the script and signature-hash rules. A valid signature shows that the required private key authorised the spend without placing that private key in the transaction.
A signature does not prove the recipient is honest or an invoice is correct. Address verification and business checks happen before signing.
How Nodes Validate and Relay
A node checks that referenced outputs exist and are unspent, values balance, scripts succeed and consensus rules are met. It may also apply local policy before storing and relaying the transaction.
A transaction accepted by one mempool is still unconfirmed. Another node may not receive it or may use different policy. Block inclusion supplies the shared chain record.
How Miners Confirm the Payment
Mining nodes select valid transactions for a candidate block. ASICs search for proof of work on the header. When a valid block is accepted by full nodes, included transactions receive their first confirmation.
Later blocks add confirmations. A miner cannot spend another user's output without satisfying its script, and a pool cannot make an invalid payment valid through extra hashrate.
Replacement, Cancellation and Mistakes
Bitcoin has no universal cancel button. An unconfirmed replaceable transaction may be replaced with another version under policy, but a confirmed transaction normally cannot be reversed.
Some wallets can redirect a replaceable payment back to the sender if the replacement reaches miners first. That is a new conflicting transaction, not deletion of the original network message.
A Safe Sending Checklist
Verify the network, address, amount, fee, wallet balance and change on a trusted display. Send a small test when the destination or process is new.
Keep the transaction identifier and wait for a suitable confirmation level. Never share a seed phrase with the recipient or a site claiming it must release a pending payment.
What to Check After Broadcast
A transaction identifier lets you follow a broadcast without revealing a seed phrase. Check that the recipient output, change output and total fee match the signed details. A peer or explorer showing the transaction means it has been observed, not that it is confirmed or irreversible.
When a valid block includes the transaction, your wallet should show one confirmation. Later accepted blocks add more. A shop, exchange or mining supplier can choose its own crediting threshold according to value and risk. That service rule is separate from Bitcoin consensus, so record it clearly and do not tell customers that every payment becomes final at one universal number.
What the Current Data Can and Cannot Tell You
Address formats and wallet interfaces change, but the input-output model remains central. Use current wallet documentation for signing and fee controls.
A transaction timestamp shown by an explorer is usually an observation or block time, not a signed creation time inside every transaction.
Legal finality, service crediting and accounting treatment can require more than protocol confirmation. Keep business evidence separately.
Decision Table
| Stage | What Happens |
|---|---|
| Build | Wallet selects inputs and creates outputs |
| Sign | Required keys authorise the input spends |
| Broadcast | Peers receive, check and relay the transaction |
| Confirm | A valid block includes it in accepted history |
A table is a starting point, not a promise. Verify current official sources and apply each detail to the decision you are actually making.
Frequently Asked Questions
Does Bitcoin Move Between Accounts?
The protocol spends earlier outputs and creates new outputs rather than updating bank-style account balances.
Why Do I Receive Change?
Inputs are spent completely, so surplus is returned as a new output.
Can I Cancel a Confirmed Transaction?
Normally no. Accepted blockchain history is not a reversible card payment.
Does the Recipient Need My Private Key?
No. The sender signs locally and publishes only the transaction and signature data.
When Is a Transaction Confirmed?
It gains its first confirmation when included in a valid block accepted by nodes.
Conclusion
A Bitcoin transaction transforms earlier unspent outputs into new spending conditions. The wallet selects, calculates and signs; nodes validate and relay; miners may include it in a block. Check recipient, change, fee and network before signing because confirmation does not include a normal chargeback.
Sources and Further Reading
- Bitcoin Developer Guide: Transactions
- Bitcoin Developer Guide: Block Chain
- Bitcoin Protocol Transaction Reference
- Bitcoin Whitepaper
Build the full picture with our Bitcoin beginner guide, Bitcoin block guide and mempool and fee operations library.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.