04 — TRACKING - explorer, mempool, pools, flows

Everything in a block is exact

A block publishes its transactions' public fields, its per-pool deltas, its coinbase and its funding-stream outputs, in full and without ambiguity. There is no candidate set to narrow here and no assumption to print, which makes this the only Tracking surface with no inference chain on it - and the reason it is worth having beside the others.
what a query can return
t-address
exact balance, history, counterparties, boundary events
z or unified address
undefined not on chain - exact with your viewing key
txid
public fields candidate sets, N_eff, links
labels
consensus > owner filing > exchange > analyst > behaviour
block - 2026-01-02 18:53:18 UTC
3,191,051

00000000012f8a4b7c6d5e3f1a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f2a1b

transactions
7
exact including the coinbase
size
21.4 kB
serialised
net pool movement
50,000.5541
positive leaves the pools
coinbase
1.5625
block subsidy, ZIP 1016
where the subsidy goes
block subsidy
1.5625 ZEC
miner
1.2500 ZEC - 80 percent
deferred lockbox
0.1875 ZEC - 12 percent, ZIP 1016
Zcash Community Grants
0.1250 ZEC - 8 percent, ZIP 1016
direct dev streams
ECC's and ZF's ended at NU6; ZCG's 8 percent did not. ZIP 271 disbursed the lockbox once, at NU6.1
shielded coinbase
ZIP 213 - the miner output is a shielded output
A

Per-pool deltas

positive leaves the pool, negative enters it - both public by construction
orchard
+50,000.5541
sapling
no movement
sprout
no movement
B

Transactions

7 - in block order
Every transaction in block 3,191,051, in block order.
txidverflowvaluesev
coinbasev5coinbase+1.5625 issuedINFO
7ae8586467...v5z to t+50,000.5541 leaving OrchardHIGH
b2c3d4e5f6...v5t to tno pool componentINFO
c3d4e5f607...v5z to z0 - intra-poolINFO
d4e5f60718...v4t to tno pool componentINFO
e5f6071829...v5t to z-118.4000 entering OrchardLOW
f60718293a...v5z to z0 - intra-poolINFO

Everything on this page is exact. A block publishes its transactions' public fields, its per-pool deltas and its coinbase in full, so there is no candidate set to narrow and no assumption to print - which is why this is the only Tracking surface with no inference chain on it.