What is a transaction, really? A signed note that spends old pieces and creates new ones
A crypto transaction doesn't move coins from one account to another. It's a signed message that spends earlier outputs in full and creates new ones: usually one for the payee, one as change, and a gap that goes to the miner as a fee.
Grandma Rosa imagines a crypto payment as a coin flying through the air from Anna's phone to hers. Anna laughs. Nothing flies anywhere.
What Anna does is write a note for the village notebook: "The 50 coins the miller paid me last Tuesday: 10 now belong to Rosa, 39 come back to me, and the last 1 is for whoever writes tomorrow's page." Then she presses her seal ring under it, a mark only she can make. The note goes round the houses. Every house checks the miller's payment is real, unspent and Anna's. Then it waits for the next page.
That note is a transaction. Not coins in motion: a signed instruction to spend an old entry and create new ones.
What it is
A transaction is a signed message that uses up earlier outputs and creates new outputs. The white paper describes it in section 9: "To allow value to be split and combined, transactions contain multiple inputs and outputs." Normally there are "at most two outputs: one for the payment, and one returning the change, if any, back to the sender" (Nakamoto, 2008).
"What is a ledger?" explains the pieces themselves, the unspent outputs. This article opens one transaction and names every part.
How it works: one real payment, taken apart
Transaction 03d236de was written into block 900,000 on 6 June 2025 (mempool.space). Amounts are in satoshis; 100,000,000 satoshis make one bitcoin (Bitcoin Core).
- The input. One entry: "output number 1 of transaction 1f815abd". That's a pointer to an earlier piece, worth 178,040,473 satoshis (about 1.78 bitcoin). The input doesn't say "from my account". It says "this piece, here".
- The signature. Next to the input sits the proof that the sender may spend that piece. The developer guide describes it as letting the network "verify that Bob owns the private key which created the public key" (Bitcoin developer guide). Anna's seal ring.
- Output 0. 1,689,000 satoshis (0.01689 bitcoin) locked to one address.
- Output 1. 176,343,013 satoshis locked to another. The ledger doesn't label either as "payment" or "change". The round one looks like a payment and the other like change coming back, but that's a guess, and explorers guess too.
- The gap. In: 178,040,473. Out: 1,689,000 plus 176,343,013, which is 178,032,013. The missing 8,460 satoshis are the fee. Nobody wrote "fee" anywhere; it's simply what's left over, and the miner of block 900,000 collected it.
- The name. The transaction's ID, 03d236de860594b8..., is a hash of the transaction itself. Change one satoshi and you'd have a different transaction with a different name.
Now the part that surprises most people. The fee had nothing to do with the 1.78 bitcoin being moved. It depends on size. This transaction has a weight of 561 units. BIP 141 defines virtual size as weight divided by four, rounded up (BIP 141): 141 virtual bytes. So the sender paid 8,460 / 141 = 60 satoshis per virtual byte. mempool.space gives the median fee rate for block 900,000 as 2 satoshis per virtual byte (mempool.space). Someone was in a hurry, or their wallet guessed high.
Why it matters
- Your coins are pieces, not a pot. Every payment spends whole pieces and usually creates change. Your wallet does this for you, quietly.
- Fees follow bytes, not amounts. A million-euro transfer and a coffee can cost the same fee. A payment that spends many small pieces costs more, because it's bigger.
- Signed means final for you. Once you sign and send, there's no cancel button at a bank. Only the miners and the rules decide.
- Everything is public. Amounts, addresses and the links between pieces are on every node's copy.
Where people get it wrong
- "I sent bitcoin from my account." You signed over pieces. There's no account in the ledger.
- "Bigger payments pay bigger fees." On Bitcoin, fees depend on the transaction's size in bytes and on how busy the network is.
- "The change went missing." It went to a new address your wallet controls. Many wallets create a fresh one each time.
- "The fee is shown in the transaction." It isn't written down. It's inputs minus outputs. The white paper's rule: "If the output value of a transaction is less than its input value, the difference is a transaction fee" (Nakamoto, 2008).
The sting: do the sum yourself
Next time you pay with crypto, open your transaction on a block explorer. Add up the inputs. Add up the outputs. Subtract. That's your fee, and you've just audited a payment without asking anyone.
Then look at the change output and check it went to an address in your own wallet. If a "helpful" app sends your change to an address you don't control, you haven't paid a fee. You've paid the stranger at the gate.
Frequently asked questions
What is a crypto transaction?
A crypto transaction is a signed message that spends earlier outputs and creates new ones. On Bitcoin, it lists inputs pointing to unspent pieces, outputs locking amounts to new addresses, and signatures proving the sender may spend the inputs.
What is change in a Bitcoin transaction?
Inputs must be spent in full, so if a piece is worth more than the payment, the rest goes back to the sender as a new output, called change. Usually it goes to a fresh address in the sender's own wallet.
How is the Bitcoin fee calculated?
The fee is the total of the inputs minus the total of the outputs, collected by the miner. The sender's wallet sets it, usually as a rate per virtual byte, so larger transactions cost more regardless of the amount sent.
What is a transaction ID?
It's a hash of the transaction's data, written as 64 characters. It names the transaction uniquely, and any later transaction that spends one of its outputs refers to it by this ID.
Can I cancel a crypto transaction?
Once a transaction is in a block, nobody can cancel it. Before that, some wallets can replace an unconfirmed transaction with a new one paying at least as much fee, a method described in BIP 125. There's no bank to call.
Sources
- mempool.space API, transaction 03d236de...a4ba in block 900,000 (6 June 2025)
- mempool.space API, block 900,000 with fee details
- Satoshi Nakamoto, Bitcoin: A peer-to-peer electronic cash system (2008)
- Bitcoin developer guide, Transactions
- Eric Lombrozo, Johnson Lau and Pieter Wuille, BIP 141: Segregated Witness (weight and virtual size)
- Bitcoin Core, src/consensus/amount.h (COIN)
- David A. Harding and Peter Todd, BIP 125: Opt-in full replace-by-fee signaling

