NODE BLOCK HEIGHT
—The tip observed by our node; it may be behind the network.
PROOF OF WORK / PUBLIC NODE OBSERVATIONS
Follow our node’s view of the chain, with the observation times and validation history alongside the numbers.
NODE BLOCK HEIGHT
—The tip observed by our node; it may be behind the network.
NODE CONNECTIONS
—This node’s peer connections, not the number of nodes worldwide.
POW DIFFICULTY
—Difficulty reported by the daemon at its current tip.
ESTIMATED NETWORK WORK
—Solutions per second across the network, estimated from recent blocks.
OBSERVATION & FRESHNESS
—Node observations refresh every 30 seconds while this page is visible. An export older than three minutes is marked stale. Block and observation times are shown in UTC.
CHAIN ACTIVITY
View confirmed transactions and our node’s mempool. Refreshes every 30 seconds; observations older than 90 seconds are marked stale.
Visible totals sum transparent outputs, including change: they are not a payment amount. The presence of shielded components does not reveal their addresses or hidden values.
Checking transactions…
Waiting for a validated observation from our node.
—
| Transaction | Block and confirmations | Visible outputs (ZCL) | Type and details |
|---|---|---|---|
| Waiting for data… | |||
The mempool is a local view. The entry time can reset if a transaction leaves and returns; it is not its first-ever observation. A transaction can disappear without confirming.
—
| Transaction | Entered this node’s mempool (UTC) | Size |
|---|---|---|
| Waiting for data… | ||
RESEARCH UPDATE / SEPTEMBER 13, 2026
The evidence now strongly supports an internal NonKYC consolidation. Its public reserve API labels all three input addresses “Deposit” and the 2,684 ZCL destination “Withdraw.” These official labels, corroborated by valid address signatures, replace our earlier unattributed lead. The historical purpose remains an inference from those labels and the transaction.
NonKYC’s All Reserves page ↗ · Public address and signature data ↗
We matched the signatures to the listed ZCL address keys and independently checked them with OpenSSL. They use the Zcash message-signing format; Zclassic’s native verifier uses a different prefix and rejects them.
Our September 12 check found empty signature data on NonKYC’s individual ZCL asset page. The separate All Reserves page and public API do publish addresses and signatures. We checked all 27 ZCL entries on September 13 at 18:28–18:32 UTC, including the four addresses in this transfer.
The signed text is “NonKYC Cryptocurrency Exchange.” It contains no balance, date, block height, wallet role or liabilities. A valid signature supports the address-key attestation; the official website supplies the organizational association. It does not prove current exclusive control, historical transaction purpose or solvency.
The 27 listed rows reported 149,575.26086405 ZCL at block 3,249,437. That is an exchange-reported, dated subset—not an independently audited reserve total. The page says addresses below $10 are not tracked. Its individual asset page reported a different, later snapshot.
The transaction spent outputs from just three addresses. Fifty came from one address: 44 receipts of 49.99 ZCL and six of 74.99 ZCL.
| Address | Inputs | ZCL spent |
|---|---|---|
| t1a7…Kit6x | 50 | 2,649.5 |
| t1fz…XiSB4L | 1 | 3.41671206 |
| t1WV…of2Yz3 | 1 | 31.0936504 |
We traced all 52 parent transactions. Fifty-one involved Sapling shielded-to-transparent transfers; none was a direct coinbase reward. All fifty receipts at t1a7… came from shielded transfers between June 3 and September 5. Their on-chain fee was 0.0001 ZCL each. Being 0.01 below round amounts does not establish an exchange withdrawal fee.
The shielded side does not reveal the original senders or customers. Input count cannot establish customer count. The small 0.01028183 ZCL output was reused 64 seconds later in another consolidation sending 2,174 ZCL to the same withdrawal address.
Research checked September 13, 2026. Our node confirmed the 52-input transaction in canonical block 3,240,270. Parent history uses public explorer records. This panel is a dated research result, not a live reserve audit.
KNOW WHAT THE NUMBERS SAY
These measurements come from the Zclassic node behind our pool. They describe that node’s current view, which can lag or lose peer connections.
The exporter’s validation method will appear with its observation.
Network solutions per second measure estimated mining work. They do not measure this website’s visitors, our pool’s own hashrate, or cloud GPU capacity.
Freshness and synchronization are separate. A new export can report an old block while the node catches up. An earlier observation stays visible with a stale label if a refresh fails; missing measurements stay unavailable.
Zclassic RPC · v2.1.2-beta6 ↗MARKET CONTEXT / USD
The market-cap comparison uses CoinGecko independently of the node feed. Its timestamps and freshness can differ from the network observation.
Loading ZCL and ZEC market capitalizations…
ZCL / ZEC
Compare the transparent rich lists, their snapshot dates, and the limits of address-based concentration measures.