Zcash Network Activity
How many Zcash transactions happen each day, how much of that activity is transparent-only, shielded-only or mixed, and which shielded pools are actually being used. This measures transaction activity — not ZEC value, and not pool balances (see Shielded Supply for that).
Most recent finalized day October 10, 2026 · coverage since August 25, 2026 · last computed Oct 11, 2026, 1:57 AM
Transaction Composition
Total Transactions
6,522
▼ −14.3% vs previous finalized day
Transparent only
3,515
53.9%
▼ −11.5% vs previous finalized day
Shielded only
968
14.8%
▼ −43.7% vs previous finalized day
Mixed
2,039
31.3%
▲ +6.1% vs previous finalized day
Shielded Activity
3,007
46.1%
▼ −17.4% vs previous finalized day
Transparent only, shielded only and mixed are mutually exclusive and always add up to the day's total — see "What This Data Means" below. Shielded Activity is different: it's every transaction that touched at least one shielded pool at all — Shielded Only + Mixed, not a fourth slice of that same partition, and never ZEC value or shielded supply.
Daily Transactions Over Time
One finalized day per bar, oldest to newest. A day only appears once every one of its blocks has been processed and the chain has proven the day is complete — never estimated, and a missing day is never shown as zero. The range control above selects a calendar window; it never fabricates a day that isn't finalized yet, so a narrow dataset simply shows fewer bars than the window allows.
Most recent finalized day
October 10, 2026
Total transactions
6,522
Transparent only
3,515 (53.9%)
Mixed
2,039 (31.3%)
Shielded only
968 (14.8%)
Shielded Pool Activity Over Time
How often each pool was touched, day by day. These are the same non-exclusive counters as the Pool Activity section below — a transaction touching more than one pool counts in each — so this is never stacked into a single total, and each pool is shown on its own scale. Ironwood activity reflects Ironwood transaction structures observed directly in the blockchain data — see Methodology below for its validation status.
September 11, 2026 – October 10, 2026
Each pool is its own independent series, on its own scale — never stacked or compared against total transactions, since a single transaction can touch more than one pool.
Sprout
latest: 0
Sapling
latest: 165
Orchard
latest: 78
Ironwood
latest: 2,832
Which Pools Are Being Used
How many transactions touched each pool on the most recent finalized day. A transaction can touch more than one pool, so these figures do not add up to the total transaction count above — each is its own independent count, not a slice of a whole.
Transparent
5,554
Sapling
165
Orchard
78
Ironwood
2,832
Sprout
0
Full daily data
Download CSV →| Date | Total | Transparent only | Shielded only | Mixed | Sapling | Orchard | Ironwood | Sprout |
|---|---|---|---|---|---|---|---|---|
| Oct 10 | 6,522 | 3,515 | 968 | |||||
| Oct 9 | 7,613 | 3,972 | 1,720 | |||||
| Oct 8 | 8,501 | 4,948 | 1,368 | |||||
| Oct 7 | 6,338 | 3,690 | 987 | |||||
| Oct 6 | 6,309 | 3,824 | 824 | |||||
| Oct 5 | 7,007 | 4,259 | 956 | |||||
| Oct 4 | 5,701 | 3,576 | 666 | |||||
| Oct 3 | 6,742 | 4,335 | 622 | |||||
| Oct 2 | 7,113 | 4,445 | 795 | |||||
| Oct 1 | 7,448 | 4,603 | 752 | |||||
| Sep 30 | 7,853 | 4,538 | 1,047 | |||||
| Sep 29 | 8,703 | 4,971 | 1,161 | |||||
| Sep 28 | 8,344 | 4,902 | 1,013 | |||||
| Sep 27 | 8,199 | 4,585 | 1,410 | |||||
| Sep 26 | 8,105 | 4,111 | 1,924 | |||||
| Sep 25 | 8,506 | 4,697 | 1,214 | |||||
| Sep 24 | 11,106 | 5,926 | 2,181 | |||||
| Sep 23 | 36,282 | 25,246 | 5,177 | |||||
| Sep 22 | 18,214 | 5,993 | 7,627 | |||||
| Sep 21 | 29,519 | 8,267 | 12,156 | |||||
| Sep 20 | 16,608 | 6,200 | 5,726 | |||||
| Sep 19 | 28,240 | 8,258 | 13,298 | |||||
| Sep 18 | 16,654 | 8,619 | 2,700 | |||||
| Sep 17 | 18,981 | 8,630 | 3,686 | |||||
| Sep 16 | 10,269 | 5,803 | 1,255 | |||||
| Sep 15 | 11,768 | 4,604 | 3,585 | |||||
| Sep 14 | 6,308 | 3,958 | 631 | |||||
| Sep 13 | 5,434 | 3,353 | 584 | |||||
| Sep 12 | 5,562 | 3,555 | 533 | |||||
| Sep 11 | 6,893 | 4,312 | 770 |
Swipe to see more columns →
What This Data Means — and Doesn't
- Transparent only / Shielded only / Mixed is an exhaustive, non-overlapping split of every transaction on a given day — every transaction falls into exactly one of these three categories, so they always add up to the day's total.
- Per-pool activity (Sapling, Orchard, Ironwood, Sprout, and the transparent touch count) is different: a transaction can touch more than one pool at once — a "shielding" transaction, for example, touches both the transparent pool and a shielded pool in the same transaction. These counts are never added together or presented as parts of a whole.
- This page counts transactions and their raw inputs/outputs/actions — never ZEC value or volume.
- A day's figures don't reveal which specific transaction did what, or who was involved — they're aggregate counts only.
Activity vs. Supply
This page and Shielded Supply measure two different things. Shielded Supply reports a balance — how much ZEC sits in each shielded pool at a given block. This page reports activity — how many transactions used each pool on a given day. A pool can hold a large balance while seeing very little daily activity, or the reverse; neither page can be used to infer the other.
Methodology & Data Source
Every figure on this page comes directly from the Zcash blockchain itself, fetched via NOWNodes (the RPC provider this implementation currently uses — it doesn't create or own the data). Each block is fetched with full per-transaction detail, and every transaction in it is classified by which pools it actually touches, based on its real transparent inputs/outputs, Sapling spends/outputs, Orchard/Ironwood actions, and JoinSplits — never guessed from a transaction's version number alone.
A day is defined as one UTC calendar day, using each block's own on-chain timestamp. It's only finalized — and only then does it appear on this page — once every one of its blocks has been processed and the chain itself has proven there are no more blocks left for that day. A day that isn't yet complete is never shown as partial or estimated data; it simply doesn't appear yet.
Show full methodology
Coinbase transactions (the one block-reward transaction every block contains) are currently included in every headline figure on this page: Total Transactions, and — because a coinbase transaction has a transparent input and no shielded component — folded into Transparent Only as well. They are also separately tracked as their own coinbaseTx counter, which isn't yet surfaced as a standalone figure here. This page does not currently offer a coinbase-excluded ("user-initiated only") view. See Independent Cross-Checks below for why this hasn't changed yet despite an open question about it.
A very small number of transactions can carry a pool field (currently only ever observed for Ironwood) in a shape this site's classifier doesn't recognize. Rather than guess whether that transaction touched the pool, it's counted separately as unmodeled and excluded from that pool's count — so a nonzero unmodeled figure means that day's pool count is a floor, not a confirmed exact total. In practice this is expected to be zero or near-zero.
Ironwood's on-chain activity is tracked and displayed like any other pool, but — unlike total transactions, transparent-only, and shielded-only, which have been independently cross-checked (see below) — its counts have not been independently validated against an external source. Ironwood's activation (mainnet block 3,428,143, July 28, 2026) and the Draft status of its governing ZIPs are documented on the Network Upgrade Tracker.
The historical window currently covers a bounded set of days as the underlying dataset is built out — coverage starts at August 25, 2026 and grows as more days are finalized. It isn't a live/real-time feed — see the freshness note near the top of this page for exactly which day is the most recently finalized one. The 30D/90D/1Y/ALL range control above the historical chart only changes how much of that window is displayed; it never synthesizes a day that hasn't actually finalized.
The full finalized dataset — every field shown on this page, for every finalized day — is available as a CSV download, free for research, journalism, or independent analysis.
Independent Cross-Checks
Selected daily transaction totals have been independently cross-checked against ZecStats, an external Zcash statistics site — not a claim of any partnership or endorsement by them. For the first five finalized days on this page, total, transparent-only, shielded-only, and mixed transaction counts all matched exactly.
Show cross-check details
For the five earliest finalized days on this page (2026-08-25 through 2026-08-29), a manual cross-check against ZecStats (zecstats.com), an independent third-party Zcash statistics site, found exact matches on:
- total daily transaction counts,
- transparent-only transaction counts,
- fully shielded (shielded-only) transaction counts, and
- aggregate cross-pool (mixed) transaction counts.
This is a meaningful check on the core classification logic, but it is deliberately narrow — it does not validate every figure on this page. Specifically:
- Ironwood activity has not been independently validated — no directly comparable external metric was found for it.
- Individual pool action counts (Sapling spends/outputs, Orchard/Ironwood actions, JoinSplits) have not necessarily been validated by this cross-check, only the transaction-level classification.
- Coinbase treatment remains an open question. ZecStats' own public description states its daily transaction metric excludes coinbase transactions, but its published figures matched this page's totals — which currently include coinbase — exactly, across all five days checked. That apparent inconsistency is unresolved; this page has not changed its coinbase handling based on it, and doesn't assume either interpretation is correct.
Wording here is kept deliberately conservative — a cross-check is a check, not a certification.
Common questions
What does this page measure?
How many Zcash transactions occurred each day, and how much of that activity was transparent-only, shielded-only, or a mix of both — plus which shielded pools (Sapling, Orchard, Ironwood, Sprout) were actually used. It counts transactions, not ZEC value or volume.
Are coinbase (miner-reward) transactions included?
Yes, currently. Each block's one coinbase transaction is included in Total Transactions, and counted as Transparent Only since it has no shielded component. This page doesn't yet offer a coinbase-excluded view — see Methodology below for the full explanation, including an open question about how this compares to other public Zcash datasets.
How is this different from the Shielded Supply page?
Shielded Supply measures a balance — how much ZEC sits in each shielded pool right now. This page measures activity — how many transactions used those pools each day. A pool can hold a large balance with very little daily activity, or the reverse; the two pages answer different questions.
Why can a transaction count toward more than one pool?
A single transaction can touch several pools at once — for example, a transaction that spends from a transparent address and creates a new Orchard note (a "shielding" transaction) touches both. Because of this, the individual pool-activity counts (Sapling, Orchard, Ironwood, Sprout) don't add up to the total transaction count, and are never presented as if they do.
What do "transparent only", "shielded only" and "mixed" mean?
These three categories are mutually exclusive and always add up to exactly the day's total transaction count. Transparent only: no shielded pool was touched at all. Shielded only: at least one shielded pool was touched, with no transparent input or output. Mixed: both a transparent component and a shielded pool were touched in the same transaction.
What does "Shielded Activity" mean?
The share of a day's transactions that touched at least one shielded pool (Sprout, Sapling, Orchard, or Ironwood) — shielded-only plus mixed combined, counted once each even if a transaction touched more than one shielded pool. It answers "how much activity involved shielding at all", as opposed to the shielded-only category above, which specifically excludes any transaction that also had a transparent component.
Why is today's activity sometimes missing?
A day only appears once every one of its blocks has been fetched and the chain itself has proven the day is complete (by producing the next day's first block). Today's — and sometimes yesterday's — figures aren't final yet, so they don't appear until that happens. A missing day is never shown as zero.
What is "unmodeled" activity?
A very small number of transactions can carry a pool field in a shape this site's classifier doesn't yet recognize. Rather than guess, those transactions are counted separately as "unmodeled" and excluded from that pool's count — so a nonzero unmodeled figure means that pool's count is a floor, not an exact total, for that day. See Methodology below.
Does this show how much ZEC was transferred?
No. This page counts transactions and the raw inputs/outputs/actions inside them — it does not report ZEC amounts, transaction values, or shielded transfer volume. Zcash's shielded design means individual transfer amounts inside a shielded pool are never publicly visible.
Can I download this data?
Yes — the full finalized daily dataset is available as a CSV file (see the download link near the daily table below), free to use for research, journalism, or your own analysis.
Zcash Explorer →
Look up an individual transaction, block or address.
Shielded Supply →
Pool balances, not activity — see how they differ above.
Zcash Privacy →
How shielded transactions actually protect your data.
Curious about Ironwood's status or what's next for Zcash? See the Network Upgrade Tracker. New to Zcash? Start with the Learn hub. Looking for ZEC trading volume instead of on-chain activity? See Zcash Volume by Exchange.
Talk Zcash network activity with the community
Join ZecZcash, our independent Zcash community on Telegram, for real-time news, price talk and discussion.
Join @ZecZcash on Telegram