01 · the claim

13 of the last 200 blocks
had no fees in their first four seconds.

187/200blocks with fees within four seconds · 93%
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: 13
median time to work: 345 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.

…6d3981afba13≥ 4,097 tx0.00182734 BTCfees
…01cb631e0f13≥ 4,097 tx0.00778987 BTCfees
…c0bed45d6e13≥ 4,097 tx0.00164112 BTCfees
…2219700df113≥ 4,097 tx0.00163857 BTCfees
…888dd8bbf713≥ 4,097 tx0.00197616 BTCfees
…0dd4966b2213≥ 4,097 tx0.00185900 BTCfees
…7080ac981111≥ 1,025 tx0.00185955 BTCfees
…a14521ce1513≥ 4,097 tx0.00157928 BTCfees
…dd814329d810≥ 513 tx0.00256973 BTCfees
…947b4da39a13≥ 4,097 tx0.00184602 BTCfees
…ad53fc746413≥ 4,097 tx0.00157490 BTCfees
…ea51d1b89710≥ 513 tx0.00167545 BTCfees
…838e4e0edc11≥ 1,025 tx0.00302733 BTCfees
…92f83a75b313≥ 4,097 tx0.00160281 BTCfees
…d974864ea313≥ 4,097 tx0.00281167 BTCfees
…4f5891b7cd13≥ 4,097 tx0.00179885 BTCfees
…c215d4896a13≥ 4,097 tx0.00253256 BTCfees
…facca93a670≥ 1 tx0.00000000 BTCno fees
…c7e89df4de13≥ 4,097 tx0.00194062 BTCfees
…95012a6f6b13≥ 4,097 tx0.00216263 BTCfees
…ef87cf28cc13≥ 4,097 tx0.00167567 BTCfees
…55f077a24513≥ 4,097 tx0.00209518 BTCfees
…53671db5db13≥ 4,097 tx0.00141448 BTCfees
…0ca3de263013≥ 4,097 tx0.00175349 BTCfees

Showing the newest 24 of 200, about 1.9 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.