04 — TRACKING - explorer, mempool, pools, flows
What a transaction publishes
A Zcash transaction publishes its version, the pools it touches, its per-pool value balance, its nullifiers, its anchors, its commitments, and its transparent inputs and outputs. All of that is exact. The fee is not among them: a fee is the difference between the outputs a transaction spends and what it pays out, and the outputs it spends belong to earlier transactions, so it is computed here rather than read - and where an earlier output cannot be resolved, this page says so instead of naming a figure. What no transaction publishes is a sender inside the pool, and no amount of arithmetic on the rest produces one - so what follows the public fields is a candidate set, its filters, and the assumptions each filter rests on.
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
not in the fixture corpus - the chain has this; this build does not
ba0783815529f9825d3d3a8c2d7f3dafe63468e4b5b60dcec61f7d54d1dee84c
This build reads committed values rather than a chain, so it can answer for the one transaction the fixture corpus carries and for nothing else. The round trip is the one it carries: 7ae85864..., the 2 January 2026 unshield that calibrated the relative amount tolerance. HANDOFF-05 puts a gateway behind this route.