Orchard actions occurring in fully-shielded transactions (no transparent inputs or outputs). These represent activity entirely within the shielded pool — z-to-z transfers, not shielding or deshielding.
The gap between total Orchard actions (dim line) and the shielded-only area shows how much Orchard activity is related to pool boundary crossings. Before Orchard activated at Network Upgrade 5 (NU5), block 1,687,104, this is zero.
Orchard Actions / Day was 704.14 on 2026-09-27, the last full day of data. That is 68.2% lower than 28 days ago, when it was 2,211.
🔗 permalink ⇆ compareOrchard actions in fully shielded transactions — no transparent inputs or outputs on either side. These are the transactions that neither enter nor leave the pool: value moving privately within it. Everything else Orchard does crosses the turnstile and is visible as a flow.
It still is not a payment count. One transaction can carry many actions, a wallet consolidating its own notes looks identical to a payment, and nothing here can tell the two apart — that is the pool working as designed. Read it as private activity, not as private payments.
The gap against total Orchard actions is the point. A rising internal share means the pool is being used as a place to transact rather than a place to park, which is the behaviour the anonymity set depends on.