04 — TRACKING - explorer, mempool, pools, flows

Follow the value

Paste an address, a transaction or a block. The transparent side of Zcash is as public as Bitcoin and is returned exactly. The shielded side is returned as bounds with the reasoning printed - or exactly, if you hold the viewing key and decrypt in your own browser. Nothing here names a person.
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
Transparent - exact

UTXOs, spends, counterparties, fees and clusters: common-input ownership, change detection, exchange shapes. Boundary events - this address shielding, or being paid from a pool - carry a pool-side estimate beside them.

Shielded - bounded

An address is never written to the chain. Without a key we show what the pool publishes around a transaction: anchor-bounded candidate sets, spent-count subtraction, time and amount echoes, fee-derived action counts and wallet fingerprints - each with its assumption and its cost.

Viewing key - exact, yours

Trial-decrypt every output with your incoming key, derive nullifiers with your full key, read your own outgoing ciphertexts. In the browser, never uploaded. The only way a shielded balance appears on this site.

A

Mempool

14 unconfirmed - 9 shielded - 1 migrations - 3 transparent - 1 not decoded - fee weather: calm
unconfirmed
14
38.1 kB - next block in about 41 s
shielded share
69%
by count - 9 of 13 decoded
value crossing boundaries
1,149.2
t to z 511.2 - z to t 15.2 - Orchard to Ironwood 500 - between pools 122.8
conventional fee
10,000
zat - ZIP 317 at 2 logical actions - 11 of 12 priced pay it
findings at high
2
both of them amount echoes
Unconfirmed transactions, newest first. 14 in the pool at height 3,456,854.
txidageverflowpoolsvalueBalancefee to Lwallet guessfindingssev
12sv6O to I+500.0000 O / -499.9950 I10,000 to 2Zodl 3.8migration - canonical 500 - anchor depth 3MED
31sv6z to z0 - intra-pool10,000 to 2not classifiedrecent anchor - depth 1LOW
48sv5t to z-311.2000 I15,000 to 3not classifiedshield from t1Qw...rY - exit candidates 0LOW
1mv5z to t+12.4000 S10,000 to 2not classifiedamount echo - fee-tolerant - 4.5 h gap - N_eff 17HIGH
2mv6O/I + t+2.8000 O / -2.7950 I20,000 to 4not classifiedorchard exit and ironwood entry in one transaction, with a transparent recipientMED
3mv4t to tno pool component10,000 to 2zcashd-stylecommon-input cluster 0x41 - change to a fresh addressINFO
3mv6z to z0 - intra-pool10,000 to 2Zodl 3.8noneINFO
4mv5t to z-200.0000 S10,000 to 2unrecognised fingerprintround amount - exit watch armedLOW
5mv6z to t+2.8000 I10,000 to 2not classifiedecho candidates 3 - N_eff 2.4 - requires disclosureHIGH
6mv4t to tno pool component5,000 to 1mining-pool payout shapefan-out across 214 outputs - periodic - pool-payout patternINFO
7mv6z to z0 - intra-pool10,000 to 2not classifiednoneINFO
1mv5S to O + t+120.0000 S / -119.9950 O15,000 to 3not classifiedpool crossing with a transparent recipient - neither a migration nor a one-directional shieldMED
8mv4t to tno pool componentnot priced - L = 2exchange sweep shapemany-to-one into t1PKBiv7... - the hot wallet Lookonchain labels Binance (analyst, precedence 4 of 5)LOW
1munknownnot decodednot measurednot decodedUNKNOWN_UNPRICEDtransaction version 7 is outside the range this decoder models (1 to 6)INFO

c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5

v6 - 12s

reconnecting - the mempool feed is reconnecting

flow
O to I - migration
valueBalance
+500.0000 O / -499.9950 I
fee
10,000 zat to L = 2 logical actions
wallet guess
Zodl 3.8
severity
MED

reasoning
  1. 01ZIP 318: one Orchard note becomes one Ironwood output, the amount is public, and the denomination is canonical.
  2. 02Counted into the migration lens as a distribution. Never attributed to a wallet - a denomination is not a fingerprint.

Assumptions are printed with every estimate, and a finding is never an identity. A transparent transaction publishes the addresses on both sides of it, and the findings above name them. What no transaction publishes is an OWNER - who holds an address is not on the chain, and where a label appears here it is an attribution by a named labeller, carried with its precedence, not a fact the chain states.

These are committed values, not a live mempool. The feed is a replay of 14 transcribed transactions and it closes and reopens on a cycle, which is why the badge above spends part of its time reconnecting - the reconnect path running in ordinary operation rather than only under fault. The gateway arrives at HANDOFF-05 and the live socket at the HANDOFF-11 cutover; nothing in this panel changes when they do.