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.
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.
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