How Bitcoin Fees Work (sat/vByte, vBytes & Blocks)

Under the friendly “send now or wait” advice sits a real, elegant market: a live auction for space inside the next Bitcoin block. Once you understand the four moving parts — blocks, the mempool, vBytes, and the fee rate — the fee stops being a number your wallet picks for you and becomes something you can read and control.

1. Blocks: limited space, every ~10 minutes

Bitcoin bundles transactions into blocks, and the network targets one new block roughly every ten minutes. Crucially, a block can only hold so much — its capacity is capped (around 4 million weight units, which works out to a few thousand typical transactions). That hard limit is the whole reason fees exist: space is scarce, so it has to be rationed somehow. Bitcoin rations it by price.

2. The mempool: the waiting room

When you broadcast a transaction, it doesn't go straight into a block. It lands in the mempool— short for “memory pool” — a holding area of all pending, unconfirmed transactions that every node on the network keeps. Miners draw from the mempool to assemble the next block. When the mempool is nearly empty, almost everything gets in quickly. When it's backed up with thousands of waiting transactions, only the top bidders make the cut.

3. vBytes: how “size” is measured

Because the constraint is space, the network charges by space — and the unit is the virtual byte (vByte). A transaction's size in vBytes depends mostly on how many inputsit has (chunks of previously received Bitcoin it's spending) and how many outputs(destinations). A simple one-input, two-output send is around 140 vBytes. If you're consolidating lots of small past payments, you have many inputs, the transaction is physically bigger, and it costs more — regardless of the dollar value.

Address type matters too. A modern native-SegWit input weighs roughly 68 vBytes, while an old-style legacy input runs about 148 — more than double for the exact same spend. Moving your coins off legacy addresses is one of the few permanent fee discounts Bitcoin offers. For a fuller anatomy of what you're actually paying for, see Bitcoin transaction fees explained.

4. The fee rate: your bid for space (sat/vByte)

You don't pay a flat fee — you set a fee rate in satoshis per vByte (sat/vByte). Your total fee is that rate times your size:

The rate is your bid. Miners want to earn as much as possible per block, so they sort the mempool by fee rate and fill the block from the top down. Bid above the current cut-off and you're in the next block; bid below it and you wait. For the practical “what number do I type in” version, see what a good fee is right now.

Putting it together: the fee auction

Now the whole system clicks into place. Limited block space (supply) meets a stream of people wanting to transact (demand). Senders bid via their fee rate; miners take the highest bids first. The result is a continuous, real-time auction:

• →Demand < supply — the mempool drains, almost any bid wins, fees fall to the floor.
• →Demand > supply — the mempool grows, the cut-off rate climbs, and low bids wait.
• →Sudden demand spike — a market move or big event floods the mempool and the winning rate jumps within minutes.

This is exactly why the answer to “what should I pay?” is always “it depends on right now.” The auction never stops moving. It's also why timing helps so much — see the cheapest time to send Bitcoin.

A worked example in real numbers

Suppose the mempool is quiet and next-block space is going for 5 sat/vByte — an illustrative figure, not today's rate. A standard 140-vByte spend costs 140 × 5 = 700 sats. Later, a wave of demand pushes the winning bid to 60 sat/vByte, and the identical transaction now costs 8,400 sats. Nothing about your payment changed; the auction did.

Now change the transaction instead of the market. Sweeping ten small native-SegWit inputs into two outputs comes to roughly 750 vBytes. At 5 sat/vByte that's about 3,750 sats; at 60, about 45,000. Same value moved, five times the size, five times the fee at every rate. Two levers, and only two: the rate the market sets and the size you bring to it. You can time the first; you control the second.

How tools read the auction for you

A live fee tracker watches the mempool directly: how many transactions are waiting, at what fee rates, and how fast blocks are clearing them. From that it can estimate the rate needed to confirm in the next block, in 30 minutes, in an hour, or eventually — the tiers you see on SatSaver. Layer in whether the backlog is growing or shrinking, and you get a genuine send-or-wait verdict instead of a raw number to interpret.

What the miner gets

Worth knowing where the money goes: the miner who builds a block collects every fee inside it, plus the block subsidy (newly issued Bitcoin). As the subsidy shrinks over time through periodic halvings, transaction fees become a larger share of what secures the network. Your fee isn't a toll to a middleman — it's a direct payment into the system that keeps Bitcoin running.

Mistakes that quietly inflate your fees

• →Trusting wallet defaults. Many wallets overbid on purpose — a fast confirmation generates fewer support tickets than a cheap one. Check the live rate before accepting the suggestion.
• →Sending at peak hours out of habit.Congestion follows human schedules, so the same transaction can cost several times more at the day's busiest point than in a quiet window. And when rates spike hard, there's usually a specific cause — see why fees get so high.
• →Ignoring UTXO hygiene.Every small deposit you receive becomes an input you'll someday pay to spend. Consolidate during a fee lull on your terms, not during a spike on the market's.
• →Panic-resending a stuck transaction.Broadcasting a duplicate doesn't work — the network sees a double-spend and rejects it. Bump the original instead, using RBF or CPFP.
• →Using on-chain for coffee-sized payments.When the fee rivals the amount, the base layer is the wrong tool — that's what Lightning is for.

Quick answers

Does the fee depend on how much I'm sending?

No. Moving 1 BTC and moving 0.001 BTC in the same-shaped transaction cost exactly the same, because both occupy the same number of vBytes.

What happens if I bid too low?

Your transaction waits in the mempool. Wait long enough and most nodes drop it entirely, at which point the coins remain spendable in your wallet as if nothing happened. A low bid is a delay risk, not a loss risk — details here. If it's already stuck, here's how to unstick it.

Can I get a refund if I overpay?

No. The full fee goes to whichever miner includes your transaction, and there's no mechanism to claw any of it back. That's the real argument for spending five seconds reading the mempool before you hit send.

How long will my chosen rate take to confirm?

Anywhere from the next block to days — it depends entirely on where your bid sits relative to the backlog. Full breakdown in how long a Bitcoin transaction takes.

The bottom line

Bitcoin fees are an auction for scarce block space. Transactions wait in the mempool, their size is measured in vBytes, and your sat/vByte rate is the bid that decides your place in line. Master those four pieces and you'll always understand whythe fee is what it is — and never feel at the mercy of your wallet's default again.

See the auction live: the SatSaver fee tracker turns the current mempool into a clear rate and a send-or-wait call, updated every 60 seconds. Data from mempool.space.