01 · the claim
7 of the last 200 blocks
had no fees in their first four seconds.
over the last 29 h · coinbase read on 200 of 200
The coinbase is the receipt. It pays the block subsidy plus the fee of every transaction in the work, so whatever it pays above the subsidy is fees the template carries. A coinbase-only template pays the subsidy and nothing else.
- no fees within 4 s
- 7
- median time to work
- 333 ms
- blocks not seen
- 0
- unreadable samples
- 0
02 · the instrument
One row per block, newest first
Measured from LA-residential, a machine outside this pool. A node timing itself reports about zero, which tells you nothing about either of us. Blocks the vantage saw no work for are counted from the gaps in block heights and from the blocks its own peers announced.
- …3c9d0873d413≥ 4,097 tx0.00290436 BTCfees
- …cd25dee1d713≥ 4,097 tx0.00372581 BTCfees
- …1fb8a06db513≥ 4,097 tx0.00692734 BTCfees
- …64443abbd213≥ 4,097 tx0.00348603 BTCfees
- …8fb1d2ff3e13≥ 4,097 tx0.00336144 BTCfees
- …762cda3ee50≥ 1 tx0.00000000 BTCno fees
- …9993d1a71113≥ 4,097 tx0.00341016 BTCfees
- …8ab3ce9f2013≥ 4,097 tx0.00362716 BTCfees
- …4a97af661413≥ 4,097 tx0.00441557 BTCfees
- …a23d61fddf13≥ 4,097 tx0.00300917 BTCfees
- …f6ea39d3ba13≥ 4,097 tx0.00270107 BTCfees
- …d46b46d28113≥ 4,097 tx0.00271165 BTCfees
- …041ed81cee13≥ 4,097 tx0.00283869 BTCfees
- …93644da5f713≥ 4,097 tx0.00315381 BTCfees
- …36e0ad9abd13≥ 4,097 tx0.00479280 BTCfees
- …65de5a678613≥ 4,097 tx0.00384228 BTCfees
- …db2310ba8313≥ 4,097 tx0.00366130 BTCfees
- …275469d56913≥ 4,097 tx0.00363272 BTCfees
- …4b42356e2d0≥ 1 tx0.00000000 BTCno fees
- …68cbe4444b13≥ 4,097 tx0.00255531 BTCfees
- …2d7f45764613≥ 4,097 tx0.00297715 BTCfees
- …79175cbd6713≥ 4,097 tx0.00329472 BTCfees
- …bff80930d613≥ 4,097 tx0.00312385 BTCfees
- …a5b13794cc13≥ 4,097 tx0.00397828 BTCfees
Showing the newest 24 of 200, about 3.3 h of the 29 h the headline counts. The rest are in the API, unabridged.
03 · verify it yourself
Measure it from your own network.
Time one trip from this browser
Your own network, your own clock. What comes back is the distance to us.
Watch a block reach you
Stay on this page. When the chain advances, we stamp the moment this pool told your browser. Your machine takes that timestamp, not ours.
waiting for the next block…
what this page cannot tell you
- Step 02 stamps an announcement arriving. A block your own node has validated is a later and stronger event. Your browser is also a weaker instrument than the vantage, and the clock it reads is yours.
- The first job on every new block is coinbase-only, because our node is still validating the block. A row reads no fees only when no template with fees reached the vantage within four seconds of that first job.
- The coinbase shows the fees the work carried. It cannot show whether a richer set of transactions was on offer at that moment; your own node’s template is the comparison for that.
- A row without a coinbase reading is judged by its branch, and any transaction counts as fees. The figure says on how many blocks the coinbase was read.
- A merkle branch proves a floor on the transaction count, and stops there. A few large transactions fill a block on a short branch, so the branch is no measure of how full the block was.
- One vantage is one place on the network. A vantage somewhere else would read different numbers, and both readings would be right.
- The window holds the most recent 200 blocks, roughly a day and a half at the current rate. Older blocks fall off it.
- The headline counts every block in that window; the strip draws only the newest 24. We print both numbers above so you can check one against the other, and the API serves the window unabridged.