Bitcoin Burger utility

Fee Estimator

Get current Bitcoin network fee recommendations

Transaction Details

Average transaction: ~250 bytes
Estimated Size Guide
• 1 input, 2 outputs: ~250 bytes
• 2 inputs, 2 outputs: ~370 bytes
• SegWit transaction: ~140 bytes

Fee Comparison

Network Information

Last Updated
Loading...
Data Source
mempool.space API
Bitcoin Price
Loading...
Fee Calculation
sat/byte × transaction size

How Bitcoin fees work

Bitcoin block space is limited. When many people send transactions at once, wallets bid for inclusion by attaching a higher fee rate. Miners generally include the most profitable (highest fee-per-vByte) transactions first.

Formula: total fee (sats) ≈ fee rate (sat/vB) × transaction virtual size (vB). This tool multiplies live recommended rates by the size you enter so you can compare priority levels in sats, BTC, and USD.

Typical sizes:a simple single-input SegWit payment is often near ~140 vB; a common 1-in/2-out spend is often cited around ~250 vB; consolidating many inputs can be much larger. Always check your wallet's estimate before broadcasting.

Confirmation targets (~10 min, ~30 min, ~1 hour) are planning guides based on current mempool conditions. They are not guaranteed—sudden demand spikes can delay lower-fee transactions.

Ways to pay less

  • • Smaller transactions: fewer inputs and outputs mean fewer vBytes.
  • • Modern address types: SegWit and Taproot usually use block space more efficiently than legacy P2PKH.
  • • Timing: weekends or off-peak periods sometimes clear with lower rates—watch live recommendations.
  • • Batching: exchanges and merchants often combine payouts; individuals can consolidate carefully when fees are low.
  • • Lightning: for small, frequent payments, Lightning Network fees can be far lower than on-chain once channels are open.

Frequently asked questions

How are Bitcoin transaction fees calculated?
Miners prioritize transactions by fee rate, typically measured in satoshis per virtual byte (sat/vB). Total fee ≈ fee rate × transaction size (vBytes). Larger transactions (more inputs/outputs) cost more at the same rate.
What is sat/vB or sat/byte?
It is the fee density: how many satoshis you pay for each unit of block space your transaction consumes. Higher rates usually confirm faster when the mempool is busy; lower rates can work when demand is light.
Why does SegWit often cost less?
SegWit (and Taproot) change how transaction weight is counted, so a typical spend uses fewer virtual bytes than an equivalent legacy transaction. Smaller size at the same sat/vB means a lower total fee.
Where do these estimates come from?
Recommended high, medium, and low priority rates are fetched from the mempool.space public API and combined with the transaction size you enter. Confirmation times are approximate targets, not guarantees.
Also on the menu

Related tools

Keep going—these utilities pair well with what you just used.