Validator Transparency Dashboard

LIVE

Solana mainnet

Find a validator

Browse the catalog below (search by name or vote key), or paste a vote account here if you already have one – same dashboard for every mainnet validator.

Example (creator’s node): Open AndrewInUA

System signals: …

Browse & search

Names and stake come from the public Stakewiz catalog. Type at least two characters to match name or vote account; leave empty for top validators by stake.

Loading catalog…

Name	Vote account	Comm.	Stake (SOL)	Jito-capable i	Vote success i
Loading…

How to read this page

1 · Trust Card
A quick at-a-glance check: what fee they take, are they alive right now, and how steady their recent voting was.

2 · Stability score
The single most important number. Higher = fewer past delinquency events and fee changes in stored history. Use this first.

3 · Profitability & Pools
Estimated yield (from public APIs) and which staking pools delegate here. Useful context, not a guaranteed payout.

4 · Recent voting (chart + numbers)
Short-term, live read from RPC. Helpful for spotting recent changes; the Stability score above is still your primary signal.

5 · Duplex summaries
Verdict = network-relative band plus snapshot depth. Signal breakdown below rolls the same telemetry into positives/cautions for this validator – orthogonal scoring paths.

Tip · At a glance
Right under this box, the green row is a quick preview of the numbers below.

At a glance The same key numbers you’ll see in the cards below, in one row

Stability –

Commission –

Status –

Recent voting –

Jito –

APY est. –

Pools –

Validator profile

–

Loading…

– Jito: –

Loading context…

This page is tied to the vote in the URL. The backend records scheduled snapshots for all mainnet vote accounts; per-validator “how much history” still grows from the first day that account appears in storage.

Trust Card

Commission (validator fee) i

–%

Lower is usually better for your net yield. 0% means the validator takes no fee here (pool/program fees may still apply). 100% means delegators effectively earn nothing – avoid.

Status (alive right now?) i

–

Quick liveness check from RPC. Healthy is what you want; Delinquent means the validator is currently missing votes – combine with the Stability score before deciding.

Recent voting % (last few epochs) i

–%

Average across the last few finished epochs. ~99 – 100% is great. Drops below ~90% in normal conditions deserve a closer look (could be temporary, but worth checking).

Last updated: –

Stability score (all-time snapshot history) i

Snapshot-only block. 100 means no delinquency and no commission changes in stored history. Coverage is network-wide; confidence still rises as more snapshots accumulate for this vote account over time.

–

/100

–

Primary scoring span: –

Loading…

–

How to use

This score reflects full stored history for this vote account (same pipeline as every other validator).
Higher is better for consistency (fewer delinquency events and fee changes).
New entries can look “early” until enough daily snapshots pile up – compare validators with similar history length when possible.
Use this as the main consistency signal; then check APY and pool context.

How to weigh things: start with the Stability score, double-check Commission and live Status for risk, then look at APY and pool presence for reward context. If two signals disagree, trust the long-term ones.

Estimated rewards & who else stakes here i

APY ≈ approximate yearly yield (estimates from public APIs). Pools delegating = how many known staking pools (Marinade, Jito, etc.) trust this validator with stake.

Stakewiz API Trillium API

APY (blended estimate) i

–%

Stakewiz APY i

–%

Trillium APY i

–%

Pools delegating i

–

Stake from known pools– SOL

Other / untagged stake– SOL

Total active stake– SOL

Public API status: –

The two cards below = recent live behavior. Use them to confirm what the Stability score above already told you. If they disagree, prefer Stability (it’s based on stored history, not a few epochs).

Recent voting (last few epochs) i

Each dot = one finished epoch. Higher is better (they voted on more of their slots). The active epoch is hidden while voting is still in progress.

Consistency %

Avg

– epochs

At a glance – recent epochs i

Solana RPC Stakewiz Trillium Jito

How many recent epochs we can see i

–

Trend (getting better or worse) i

–

Steadiness between epochs i

–

Reward signals (Jito + APY estimates) i

–

Signal breakdown i

Loading…

–

What looks good

Loading…

What to watch

Loading…

Confidence: –

Open another validator

Search by name below (e.g. “Coinbase”, “Marinade”), or paste a vote account. Optional name overrides the auto-detected display name in the new tab.

Tip: pick a row from the dropdown to auto-fill, or paste a raw vote account.

Compare on this page

Compare current validator with

Tip: Validator A is the currently opened validator on this page. Validator B is the vote account you pick or enter above.

This link saves your current view. If comparison is active, it also includes vote2 so others open the same A vs B comparison.

Roadmap

Direction – make every insight actionable for delegators (what to do next, not just charts), then harden the same signals as open infrastructure so wallets, explorers, and teams can build on one transparent pipeline – not a one-off page.

Done: All-time snapshot-based stability scoring

Done: Validator comparison on the same page

Done: Full-network snapshot collection (scheduled; all vote accounts from RPC)

Done: Directory on home – search by name or vote key (open home)

Done: First-glance KPI strip + richer directory & pickers (context before you open a profile)

Next: Per-epoch detail page

Next: Delinquency alerts & proactive signals

Next: Actionable insight layer – clearer next steps, exports, and “what changed” across the page

Next: Builder-ready surface – documented HTTP APIs, stable metric definitions, embed / reuse patterns

System signals: checking…

Runtime sources: checking…

Source model. Live inputs come from Solana RPC + Stakewiz + Trillium + Jito proxy. Stability uses backend snapshot history plus current public inputs.

Methodology. Main stability ring uses all stored snapshots for the opened vote account. Highlighted secondary score uses the recent snapshot window. Recent voting consistency is short-window RPC context. Two validators can both be “fully covered” by collection but have different history lengths until enough days of snapshots accrue.

History model. Scheduled jobs snapshot all mainnet vote accounts returned by RPC and write shared rows in storage. Opening a page only sends an optional analytics ping (does not gate whether snapshots exist). Everyone reads the same dataset for a given vote key.