Sending a Transaction and Its Fee

You tap Send, pick an amount, and your wallet does something that looks suspiciously simple. Under the hood, it’s anything but. To pay you don’t “withdraw” a number — you reach into a pile of coins you already hold, hand whole ones over, get change back, quietly tip a miner, and then broadcast the whole bundle into a global waiting room to be picked up. This lesson follows one bitcoin payment along that entire journey, and finally demystifies the part everyone grumbles about and almost nobody understands: the fee — where it comes from, who gets it, and why it has nothing to do with how much you’re sending.

Your Balance Is a Pile of Coins (UTXOs)

You met UTXOs back in crypto-basics; here’s the deepened version, because everything in this lesson hangs off it. UTXO stands for Unspent Transaction Output. Every time someone pays you, the payment shows up as an output of their transaction. Until you spend it, it sits on the chain unspent — like an uncashed cheque made out to your keys. So your “balance” is really a wallet full of discrete coins of various sizes: maybe a 0.5 BTC chunk, a 0.2 BTC chunk, and a 0.1 BTC chunk, adding up to the 0.8 BTC your app shows.

The crucial rule — the one that drives change, fees, and coin selection — is that you spend UTXOs whole. Just as you can’t tear a 20-dollar bill in half, you can’t spend “part of” a UTXO. To pay, you consume one or more whole coins as inputs and create brand-new coins as outputs. The chain’s record of what you own is always just the set of outputs nobody has spent yet.

Watch the difference between this coin-like model and a plain bank balance. Hit “Send a payment” and keep your eye on the left (UTXO) side: a whole coin lifts out toward the recipient, and a smaller change chip floats right back to you.

Inputs, Outputs, and Change

A bitcoin transaction has two sides:

• Inputs — references to UTXOs you own, each one unlocked by your signature (lesson 5). An input says “I’m spending this specific coin, and here’s the proof I’m allowed to.” The inputs must add up to at least the amount you’re sending plus the fee.
• Outputs — the new coins this transaction creates: one (or more) to the recipient, and usually one back to yourself.

That last one is change. Because you spend whole coins, your inputs almost always exceed what you owe — so the leftover is sent back to you as a new UTXO at a change address your wallet controls. It’s the digital twin of paying a 7-dollar coffee with a 20-dollar bill and getting 13 dollars back. The twist: in Bitcoin you create the change output yourself, as part of the very same transaction. There’s no cashier handing it over; your wallet writes the change output in for you.

Where the Fee Actually Comes From

Here’s the part that surprises everyone. A Bitcoin transaction has no fee field at all. Instead:

Let’s make it concrete. Say you spend a single 0.5 BTC coin to send 0.3 BTC, and you set your change output to 0.1999 BTC:

Inputs total 0.5; outputs total 0.4999; the 0.0001 BTC gap is the fee. Nobody wrote “0.0001” into a fee box — it’s just the slice you chose not to send anywhere, and the miner who packs your transaction into a block scoops it up.

Fee Rate: Paying by Size, Not Amount

If the fee isn’t a percentage of the amount, what does set it? Size. Miners care about one thing: getting the most fee revenue into a block that has a fixed capacity. So they value a transaction by its fee rate — fee divided by size — measured in satoshis per virtual byte (sat/vByte). (A satoshi is the smallest unit of bitcoin, one hundred-millionth of a BTC. A virtual byte is Bitcoin’s way of measuring how much block space a transaction occupies.)

You don’t really choose a total fee; you choose a fee rate, and the total falls out of rate × size. The size, in turn, depends mostly on how many inputs you bundle. A payment that gathers ten little coins is physically bigger — ten signatures to include — than one that spends a single fat coin, even if the second moves a hundred times more money.

Miners fill each block highest-fee-rate first, so a higher sat/vByte jumps the queue. We’ll watch that auction in the next section.

From Broadcast to Confirmation

Every Bitcoin payment runs the same relay. Here’s the whole trip:

A confirmation is just a block stacked on top of the block holding your transaction. One confirmation = your transaction is in the latest block. Six confirmations = five more blocks have piled on top. Why count them? Because reversing your payment would mean re-mining your block and every block above it faster than the rest of the network mines new ones — exactly the proof-of-work tug-of-war from lessons 2–3. The deeper your transaction is buried, the more work an attacker must redo. So more confirmations = harder to reverse = safer, and ~6 is the common “very safe” threshold for large amounts.

When the Mempool Gets Crowded

Each block holds only so many virtual bytes, and a new one arrives roughly every ten minutes. When more people want to transact than fit in the next few blocks, the mempool fills up and a bidding war breaks out: the going fee rate climbs as everyone tries to outbid everyone else for the limited seats. In quiet times the mempool nearly empties and a few sat/vByte sails through; in a frenzy the clearing rate can spike dramatically. Nothing about your transaction changed — the competition did.

Drag your fee up and down below, hit produce next block, and watch whether your transaction grabs a slot or gets left in the mempool. There’s no magic “correct” fee — it’s whatever beats the others bidding for the same block.

What if you already broadcast a transaction with too low a fee and it’s stuck? It is not lost forever. You have options:

• Replace-by-Fee (RBF): re-broadcast the same transaction with a higher fee rate, replacing the stuck one and jumping the queue. (Your wallet must have flagged it as replaceable.)
• Child-Pays-For-Parent (CPFP): spend the stuck transaction’s change output in a new, high-fee child transaction. A miner who wants the juicy child fee must include the cheap parent too, dragging both into a block.
• Just wait: if congestion eases, even a low-fee transaction can confirm later. And if it never confirms, it eventually drops out of mempools and the coins are simply spendable again — they were never gone.

The Big Picture

One payment: built from coins you hold, signed, broadcast, parked in the mempool, and bid into a block whose miner pockets the leftover as a fee. Chunk the whole journey into one picture:

A mixed recap — it pulls from everything above:

Key Takeaways

You’ve now followed a payment from your screen into a block — but who actually checks that your transaction is valid before relaying or mining it? Next: nodes and full verification, the unsung machines that independently enforce every rule of Bitcoin so no one has to be trusted.