Blockspace Lab
Simulate Bitcoin, Bitcoin Cash, or Litecoin congestion. Choose network rules and traffic, then watch backlog, fees, and confirmation time change.
Blockspace simulation workbench
Simulation clock
Advance simulated time
How the model works
Transactions enter five fee bands. With fee-priority mining enabled, blocks drain the highest-fee bytes first, so sustained overload becomes backlog and can move the next-block fee upward. Turn priority off to model fee-neutral block assembly instead.
The displayed fee estimates the marginal rate inside the lowest fee band touched by the current block candidate. It is not the fee required to empty every queued byte, so lower-fee backlog alone does not raise the estimate. For a guided example, read how blockchain congestion builds and fees rise.
Timing uses either the target interval or an untruncated, seeded exponential distribution. Difficulty algorithms are represented by their long-run targets under steady hash rate; hash-rate shocks and retarget lag are outside the model. The demand rail is therefore a directional signal, not a confirmation promise.
BTC and LTC base capacity is measured in BIP 141 virtual bytes, so SegWit's witness discount is already included in the one-million-vbyte budget. Litecoin MWEB remains a separate opt-in block with its own weight rules and is not pooled into the transparent mempool.
BCH capacity is measured in serialized bytes. After each block, the lab applies the published ε + β ABLA transition using production constants, ordered integer divisions, the 32 MB floor, and the 2 GB external cap.
Reported profiles translate disclosed Visa processing, Swift FIN messaging, or Fedwire transfer counts into an average arrival rate, then apply a representative daily or business-day rhythm. They are educational load analogs, not historical traffic replays.
One reported event becomes one simulated transaction. The selected transaction size, fee lanes, proof-of-work timing, and block rules still belong to this model. A card authorization, financial message, bank transfer, and permissionless settlement therefore remain distinct even when their event counts are compared.
This is an aggregate educational model, not a live node or fee oracle. Capacity values represent protocol limits; miner template reserves and editable relay-policy floors are not consensus rules.
Per-node mempool caps, rolling eviction fees, package relationships, propagation, reorgs, and byte-exact block overhead remain outside the model. For current network observations, open TX::Watch.
Recent graph samples remain exact. Older samples retain real first, last, low, and high observations from evenly spaced time buckets, preserving the run's shape without drawing every sample. Between observed points, queue values are labeled as estimates while discrete fee and capacity state stay stepped to the last sample.
- Bitcoin BIP 141 — block weight and virtual size
- Bitcoin Core — mining and relay policy defaults
- Bitcoin Core — network timing parameters
- Litecoin — base block consensus limits
- Litecoin — network timing parameters
- Litecoin — MWEB weight budgets
- Bitcoin Cash — Adaptive Blocksize Limit Algorithm
- Bitcoin Cash Node — timing and ABLA chain parameters
- Bitcoin Cash Node — mining fee-rate selection
- Bitcoin Cash Node — mempool limits and effective fee floor
- Visa FY2025 — processed transaction volume
- Swift Annual Review 2025 — FIN message volume
- Fedwire Funds Service — 2025 transfer volume