ZEC View
English简体中文

Zcash guides

Zcash Hashrate: Network Mining Statistics

Quick Answer

The pinned zcashd getnetworksolps interface reports estimated network solutions per second based on a selected block window. A hashrate number without its estimator, window, height and observation time is not a reproducible network measurement. The preserved zcashd mining source describes getnetworksolps as an estimate based on the last n blocks.

Key Takeaways

  • Network solution rate estimates mining work over an observation window.
  • Zcash node RPC documentation describes a block-window estimate.
  • A provider hashrate value needs its actual unit, window and source date.

Current provider observation

Issued Supply

17,047,126.7679 ZEC

Observed · ZecStats

Latest provider data — short shared cache

2026-10-17: 16990412.66554482026-10-18: 16992201.72804482026-10-19: 16994004.85304482026-10-20: 16995786.10304482026-10-21: 16997582.97804482026-10-22: 16999362.66554482026-10-23: 17001151.72804482026-10-24: 17002956.41554482026-10-25: 17004743.91554482026-10-26: 17006536.10304482026-10-27: 17008323.60304482026-10-28: 17010123.60304482026-10-29: 17011917.35304482026-10-30: 17013695.47804482026-10-31: 17015486.10304482026-11-01: 17017289.22804482026-11-02: 17019828.29054482026-11-03: 17020878.29054482026-11-04: 17022651.72804482026-11-05: 17024451.72804482026-11-06: 17026222.547548362026-11-07: 17027955.88216342026-11-08: 17029754.111272542026-11-09: 17031550.835059592026-11-10: 17033340.001390422026-11-11: 17035160.671897542026-11-12: 17036936.995098682026-11-13: 17038730.662274692026-11-14: 17040540.96092212026-11-15: 17042337.30360104

Mini-chart: published daily observations, separate from current value.

Block Height

3,583,604 blocks

Observed · ZecStats

Latest provider data — short shared cache

2026-10-17: 35204982026-10-18: 35216442026-10-19: 35227982026-10-20: 35239352026-10-21: 35250872026-10-22: 35262232026-10-23: 35273702026-10-24: 35285242026-10-25: 35296712026-10-26: 35308182026-10-27: 35319592026-10-28: 35331122026-10-29: 35342572026-10-30: 35353972026-10-31: 35365422026-11-01: 35376992026-11-02: 35393252026-11-03: 35399972026-11-04: 35411322026-11-05: 35422842026-11-06: 35434432026-11-07: 35467702026-11-08: 35502222026-11-09: 35536732026-11-10: 35571122026-11-11: 35606112026-11-12: 35640282026-11-13: 35674732026-11-14: 35709522026-11-15: 3574404

Mini-chart: published daily observations, separate from current value.

Total Shielded ZEC

4,932,795.3948 ZEC

Observed · ZecStats

Latest provider data — short shared cache

2026-10-17: 4964457.847687042026-10-18: 4963836.24466042026-10-19: 4959779.778871692026-10-20: 4960405.658913242026-10-21: 4956042.879768132026-10-22: 4960464.515884862026-10-23: 4962751.09800938052026-10-24: 4963432.392674082026-10-25: 4968466.933257662026-10-26: 4959670.375032572026-10-27: 4954646.261944252026-10-28: 4957708.3283168512026-10-29: 4957070.0725966392026-10-30: 4961051.2573430592026-10-31: 4968466.652658552026-11-01: 4969906.0167252792026-11-02: 4975876.1510958212026-11-03: 4978047.657988282026-11-04: 4979301.61977042026-11-05: 4980243.706618242026-11-06: 4980723.809168452026-11-07: 4988141.324479812026-11-08: 4986232.5331670712026-11-09: 4990559.957292612026-11-10: 4989013.204933342026-11-11: 4989368.868450652026-11-12: 4930710.038022532026-11-13: 4935078.442589842026-11-14: 4935558.86568382026-11-15: 4978913.05724051

Mini-chart: published daily observations, separate from current value.

Shielded Supply

28.94%

Observed · ZecStats

Latest provider data — short shared cache

2026-10-17: 29.2191716906003372026-10-18: 29.212437117362082026-10-19: 29.1854675914315182026-10-20: 29.1860913572251982026-10-21: 29.1573389355985632026-10-22: 29.1802970115990872026-10-23: 29.1906758871101282026-10-24: 29.1915845184211982026-10-25: 29.2181226482085462026-10-26: 29.1633190026545462026-10-27: 29.130714922764512026-10-28: 29.145633764997592026-10-29: 29.1388088110445762026-10-30: 29.1591633560446162026-10-31: 29.1996750640551962026-11-01: 29.205039358059362026-11-02: 29.2357599980025642026-11-03: 29.2467143763880562026-11-04: 29.2510338537150862026-11-05: 29.2534748617728552026-11-06: 29.253252124826912026-11-07: 29.2938351437992252026-11-08: 29.279533342566142026-11-09: 29.301852812014632026-11-10: 29.2896942380419252026-11-11: 29.2886516572836372026-11-12: 28.9412940802741442026-11-13: 28.96388551710932026-11-14: 28.9636278390584962026-11-15: 29.214966049219477

Mini-chart: published daily observations, separate from current value.

The source-linked reference text below retains its documented dates; live measurements do not rewrite historical facts or establish consensus activation.

Compare network estimates with local solution rates

Sol/s means solutions per second; GSol/s is the giga-scale unit. Neither rate is a miner count, a difficulty value or a profit estimate.

Three rates that answer different mining questions
MeasurementScope and windowUseful comparison
Provider-reported network estimateZecStats network field; averaging window unknown. Keep its source observation and retrieval times.Read the current provider value, but do not assume it uses the pinned RPC default.
Pinned getnetworksolps RPC estimateChain-derived estimate; the cited implementation defaults to 120 blocks and height -1. Not an RPC call made by this site.Compare observations only when software, selected window, height, unit and time are documented.
Local getlocalsolps rateLocal average since that node started; not the network total or an inventory of all mining devices.Use for local activity within that scope, not as a substitute for network hashrate.

What the primary RPC source defines

The preserved zcashd mining source describes getnetworksolps as an estimate based on the last n blocks. Its documented default is 120 blocks and height -1; the help says blocks -1 selects the difficulty averaging window, while a height can target the time a particular block was found.

These are source-code interface definitions at the cited commit, not parameters verified for every provider or current deployed node. The result unit in that interface is solutions per second, not a coin balance, price or transaction count.

Local speed and network estimates answer different questions

The adjacent getlocalsolps interface describes the average local solutions per second since the node started. That differs from a chain-derived network estimate.

A chart title should not collapse local miner performance and total network estimation into the same series. To compare two observations, identify the method and scope before comparing magnitude.

A shorter or different block window is a methodological difference, not automatically an arithmetic error or evidence that one source is dishonest.

What the current provider record does not establish

The existing ZecStats summary contains a formatted hashrate field and attributes network data to cipherscan, but the provider averaging window remains unverified in this project. The summary is third-party evidence, not an independent RPC call to a locally managed node.

The field is not promoted to a verified current chart here. Source-generated time, retrieval time and arithmetic validation have different meanings; an upstream success or stale flag is not a disclosure of estimator parameters.

The local network dashboard instead exposes the separately validated pool-history scope it actually implements.

How to build a comparable history

Preserve the node/software version or provider method, selected blocks, height, observation timestamp and unit for each record. Keep changes in estimator configuration visible instead of joining unlike values into a smooth trend.

Missing samples should stay missing; a shorter history should not be filled with report examples or invented observations. A source correction needs its original field and date so affected charts can be isolated.

This guide is for researchers and operators checking measurement definitions, not choosing hardware, estimating mining profit or predicting the asset price.

FAQ

Is hashrate here a direct count of all mining machines?

No. The inspected RPC defines a chain-derived solutions-per-second estimate, not an inventory of mining hardware.

What is the documented default window?

The cited getnetworksolps interface defaults to 120 blocks; the provider’s actual window is not verified here.

Does this site run its own hashrate node?

No. The source implementation is preserved, but no independent current-node query or measured hashrate history is available.

Can a zero response be assumed to mean no mining?

No. The pinned function also returns zero for missing/insufficient chain context or a zero time range.

Sources and Methodology

Page updated: . Source observation dates remain separate.

The page update is an editorial date. Live source observation and retrieval times appear above; the pinned RPC source keeps its own version and original source-check date.

zcash-rpc-mining

Source checked: 2026-10-01T20:17:17.587777+00:00

Source version and supporting details
  • Pinned getnetworksolps help describes estimated network solutions per second from a block window.
  • Default blocks=120 and height=-1; blocks=-1 selects the difficulty averaging window.
  • Pinned GetNetworkHashPS uses chain work difference and observed minimum/maximum time over the selected window; zero time range returns zero.
  • getlocalsolps is a separate local average since node start.

558f686599586f55def3db86955d74d3be44605e
34dcdf822e713cf4d31f05059e0d72939eb38b78df41d46959e2533f7a1d0fb7

Methodology and technical limitations

Read the estimator rather than only the method name

The implementation delegates to GetNetworkHashPS despite the public solutions-per-second name. It selects a chain index, traverses the lookup window, records the minimum and maximum block time, and divides the chain-work difference by that time range. The pinned source returns zero for cases including no useful chain index or a zero time range. This explains the behavior of that implementation; it is not proof that another dashboard uses exactly this function or that a displayed zero always means no miners. No running node is used by this project.

Method and limitations

The method explanation is a reading of one immutable zcashd source file saved by successful direct HTTP and validated by SHA-256. It has not been compiled or compared with a current-node hashrate query. The existing provider snapshot has its own stored source timestamp but no independently established averaging-window contract. Differences across software or protocols require fresh primary evidence, and this page deliberately does not claim a live verified network-hashrate feed.

Source dates describe the referenced observation or document, not a live price. How data is checked · Corrections