Bitcoin Blockspace
Test a fee scenario at the Settlement Bench, then inspect one node’s queue and a recent block sample. Model assumptions and source readings are kept separate.
Network readings
PartialPage evaluated · 1 Oct 2026, 04:17 UTC
Local model · no wallet required
The Settlement Bench
Space, not the amount sent. Explore what a transaction’s virtual size and a fee rate add up to. This is arithmetic, not a quote or a promise of confirmation.
Or enter your wallet’s virtual size, not its raw byte size.
Illustrative starting rate · not a source reading
How the example sizes are built
Each example assumes a 72-byte signature including the sighash byte and a 33-byte compressed public key per input. Actual signatures, scripts, input selection and change can alter the size.
One input · two outputs: 113 base bytes × 4 + 110 witness-related bytes = 562 weight units. Divide by 4 and round up: 141 vB.
Four inputs · two outputs: 236 base bytes × 4 + 434 witness-related bytes = 1378 weight units. Divide by 4 and round up: 345 vB.
Base bytes: 10 overhead + 41 per input + 31 per output. Witness-related bytes: 2 marker/flag bytes + 108 per input. All example counts use one-byte lengths.
Definitions: BIP141 weight and virtual size; transaction serialization.
02 / Your scenario · calculated locally
282 sats
141 vB × 2 sat/vB, rounded up to a whole satoshi.
Size: one input · two outputs example.
| Rate · sat/vB | Fee · sats |
|---|---|
| 1 | 141 |
| 2 | 282 |
| 5 | 705 |
| 10 | 1,410 |
No send amount, address or wallet connection is needed. Inputs stay in this page’s memory; this bench does not send or save them. Reloading resets the example.
Model settlement-v1: ceiling(vB × sat/vB). The 100,000 vB and 100,000 sat/vB limits are tool bounds, not validity or relay checks. This does not model unconfirmed ancestors, replacement fees, child-pays-for-parent, dust, or wallet policy. Check the wallet’s final transaction size and fee. No confirmation time or personalised recommendation is supplied.
The observed network
Read the queue, not a promise
Source observation time is not supplied. Responses use a two-minute revalidation policy; page evaluation does not reset their age.
Tip height
969,391
Latest block returned by the public node.
Queue
43.4blocks
One block equivalent is one million vbytes.
Transactions waiting
79,976
0.0914 BTC in offered fees
Next-block fee
2.52sat/vB
Estimator, not a guarantee.
Miner fee share
0.45%
Across 15 recent blocks; all fee and reward inputs required.
Fee ladder
What the estimator returned
sat/vB
Pressure reading
backlogged, cheap
The queue is deep while the source estimates a low next-block fee. Queue depth alone does not set the fee; inclusion remains uncertain. A mempool is local to a node, so another node can see a slightly different queue.
Recent block interval
8m 50s
Average across the returned block sample.
Full blocks
93%
Weight at or above 3.9 million units.
Fees per block
0.0142BTC
Recent sample average; every block needs a fee value.
Transactions per block
4,737
Recent sample average.
Readings are available; a common source observation time is not supplied.
- Source observation
- Not supplied
- Page evaluated
Responses use a two-minute revalidation policy and can have different ages. Endpoint links can return a later reading; this is not an archived receipt.
One node’s mempool, not the whole network. Fee estimates do not guarantee confirmation.
Why it matters
Bitcoin does not sell “transactions per second.” It sells scarce, ordered settlement space. The queue shows demand for that space; the fee share shows how much miners earned from users rather than new issuance.