Solana Network Health Dashboard

Solana Network Health Dashboard delivers real-time Solana network metrics in a single run — TPS (real vs. vote), epoch progress, supply figures, validator count, Nakamoto coefficient, and SOL price — using the public Solana JSON-RPC and CoinGecko APIs. No API key required. Flat $0.005/run.

Solana's performance metrics are fundamentally different from Ethereum: TPS is high but vote transactions dominate, epochs drive staking reward distributions, and the Nakamoto coefficient measures decentralization health. This actor structures that data for dashboards, alerts, and time-series monitoring.

---

Why use Solana Network Health Dashboard?

1. Real vs. vote TPS — Solana's advertised TPS includes validator vote transactions, which are infrastructure overhead, not user activity. The tps_real metric shows actual user transaction throughput. A rising vote/real ratio signals network infrastructure activity without user growth.
2. Epoch-based automation — Staking rewards are distributed at epoch boundaries (~2-3 days). Monitor hours_to_epoch_end to time staking entries, validator node operations, or epoch-aligned analytics.
3. Validator health monitoring — Track active_validators vs. delinquent_validators to assess network liveness. Delinquent validator spikes can precede network instability.
4. Nakamoto coefficient for decentralization — The minimum number of validators needed to control 33% of stake. A low Nakamoto coefficient means higher centralization risk. Track it over time.
5. Supply inflation tracking — Monitor circulating supply growth epoch-over-epoch as staking rewards are distributed. Essential for modeling SOL supply-side pressure.

---

How to use

1. Open the actor on Apify Store and click Try for free.
2. Enable includeValidators if you want Nakamoto coefficient and validator counts (adds ~2s).
3. Click Start — returns a flat list of metric records plus a SNAPSHOT key-value object.

---

Input

Field	Type	Default	Description
includeValidators	boolean	false	Include active/delinquent validator counts and Nakamoto coefficient

---

Output

Each row is one metric:

{
  "metric": "tps_real",
  "value": 1680.3,
  "unit": "tx/s",
  "category": "network",
  "description": "Real user TPS (excl. vote transactions)",
  "fetched_at": "2026-08-29T14:00:00+00:00"
}

A SNAPSHOT object is saved to Key-Value Store with all metrics as key-value pairs for direct programmatic access.

Metrics reference

Metric	Unit	Category	Description
tps_total	tx/s	network	Total TPS including validator votes
tps_real	tx/s	network	Real user TPS (non-vote)
tps_vote_pct	%	network	Share of transactions that are validator votes
current_epoch	—	economics	Current epoch number
slot_height	slot	economics	Current absolute slot
epoch_progress_pct	%	economics	Current epoch completion percentage
hours_to_epoch_end	hours	economics	Estimated hours until epoch boundary
all_time_tx_count	txs	economics	Total confirmed transactions ever
total_supply_sol	M SOL	economics	Total SOL supply (millions)
circulating_supply_sol	M SOL	economics	Circulating SOL (millions)
circulating_pct	%	economics	Circulating / total ratio
sol_price_usd	USD	market	Current SOL price
sol_24h_change_pct	%	market	24h price change
active_validators	—	validators	Active validators (when enabled)
nakamoto_coefficient	—	validators	Min validators to control 33% of stake

---

Cost estimation

Flat rate: $0.005 per run — all metrics included.

Use case	Runs	Estimated cost
Single snapshot	1	$0.005
Hourly monitoring (24h)	24	$0.12/day
Daily SOL network report	1/day	~$0.15/month
Per-epoch monitoring (~2.5d)	12/month	~$0.06/month

---

FAQ

Why is total TPS so much higher than real TPS? Solana's consensus requires every validator to vote on every block. These vote transactions make up 70–85% of all on-chain activity. They're real transactions but represent network infrastructure overhead, not user activity. tps_real filters these out.

How long is a Solana epoch? Each epoch is approximately 432,000 slots. At the target 400ms block time, that's about 2 days and 2 hours per epoch. The actual duration varies with network performance. Staking rewards are distributed at each epoch boundary.

What's the Nakamoto coefficient? It's the minimum number of validators that would need to collude to control 33% of staked SOL — the threshold for a Byzantine fault. A higher number means better decentralization. Solana's coefficient has historically ranged from 19 to 31.

Does it support Solana devnet or testnet? Currently uses api.mainnet-beta.solana.com (mainnet). Devnet/testnet support is not included.

---

Data sources

• Solana JSON-RPC: api.mainnet-beta.solana.com (public, no authentication)
• CoinGecko: Free API for SOL price and market data

---

Related actors

• Bitcoin Network Health Dashboard — Same metrics format for Bitcoin (hash rate, NVT, MVRV, mempool)
• Crypto Whale Flow Monitor — On-chain whale activity on Ethereum (complements Solana network metrics)
• Solana Memecoin Launch Tracker — New token launches on Solana (leading indicator of Solana network activity)

Feedback

If this actor is useful, a quick review helps other Solana developers find it: Leave a review on Apify Store

---

Keywords: Solana, blockchain health, TPS, validator, Nakamoto coefficient, epoch, SOL supply, network monitor, crypto infrastructure, stake distribution, Solana RPC, DeFi, web3 analytics