Solana validator network report

Solana Validator Leader Slots Report

Review how Solana leader slots relate to validator stake, epoch context, and low-latency infrastructure planning.

Data source

Solana Gossip + vote accounts

Updated Oct 02, 2026, 05:06 PM UTC

Schedule epoch

1,047

Leader slots

431,916slots

Leader validators

664validators

97.1%

Top leader

17,628slots

Figment

4.1%

Network intelligence

Network state, leader timing, and validator evidence in one report.

This panel adds live slot context, leader-window evidence, validator performance rows, and production samples to the existing reports without pretending unsupported data is already resolved.

leader window loadingperformance loading

Current slot

Leader feed loading · updated waiting

Observed slot time

Target 400 ms · epoch - complete

Transaction sample

- non-vote · - vote

Leader production sample

- scheduled · - skipped · skip -

Leader now

Resolving leader

Waiting for leader window

Slot

Window

Next different leader

Waiting for next leader group

Network activity evidence

Non-vote transactions

Vote transactions

Performance rows

Top leader-slot validators

Validators with the most scheduled leader opportunities in the joined snapshot.

Figment

4.1%

17,628 slots

Helius

3.6%

15,428 slots

binance staking

2.8%

12,064 slots

Bitwise Onchain Solutions

2.6%

11,232 slots

Jupiter

2.6%

11,192 slots

Kraken 2

2.1%

8,896 slots

Ledger by Figment

8,748 slots

Everstake

1.7%

7,412 slots

Galaxy

1.6%

6,952 slots

Staking Facilities | MEV 🔥

1.5%

6,408 slots

Top countries by leader slots

Country-level share of scheduled leader slots across geolocated validators.

Germany

186 validators · 34.6%

149,644 slots

Netherlands

117 validators · 19.5%

84,348 slots

United States

118 validators · 14.7%

63,424 slots

United Kingdom

32 validators · 9.2%

39,908 slots

Japan

53 validators · 5.7%

24,668 slots

Lithuania

17 validators · 4.4%

19,056 slots

Singapore

43 validators · 4.2%

18,332 slots

Sweden

9 validators · 1.9%

8,236 slots

Ireland

6 validators · 1.3%

5,484 slots

France

11 validators · 1%

4,264 slots

Hong Kong SAR China

15 validators · 0.6%

2,668 slots

Canada

10 validators · 0.6%

2,592 slots

Switzerland

1 validators · 0.5%

1,944 slots

Brazil

13 validators · 0.3%

1,444 slots

South Korea

1 validators · 0.3%

1,288 slots

Top cities by leader slots

City-level clusters of scheduled block production across geolocated validators.

Frankfurt am Main

109 validators · 28.8%

124,388 slots

Amsterdam

76 validators · 13.3%

57,232 slots

London

25 validators · 8.7%

37,756 slots

Tokyo

45 validators · 5%

21,508 slots

Lelystad

22 validators · 4.6%

19,668 slots

Šiauliai

17 validators · 4.4%

19,056 slots

Singapore

43 validators · 4.2%

18,332 slots

Ashburn

3 validators · 2.8%

12,292 slots

New York City

17 validators · 2.6%

11,064 slots

Eschborn

36 validators · 2.4%

10,564 slots

Offenbach

35 validators · 2.4%

10,292 slots

Los Angeles

18 validators · 2.1%

8,872 slots

Stockholm

9 validators · 1.9%

8,236 slots

Newark

9 validators · 1.6%

6,852 slots

Boardman

1 validators · 1.3%

5,528 slots

Key signal

Epoch context

Leader slots are evaluated inside the current epoch, so slot counts should be read together with epoch progress.

Key signal

Validator opportunity

Leader-slot counts show how many block-production opportunities a validator is scheduled for, not whether every opportunity performs equally.

Key signal

Network placement

Applications that react to Solana events can use leader context to reason about geography and network path quality.

What this report answers

This page explains why leader slots matter for Solana validators, RPC operators, low-latency applications, and trading systems. Use it to connect scheduled block-production opportunities with the live validator table.

How to read the data

The live rankings join validator directory data, vote accounts, Gossip metadata, and current leader-schedule counts. Because this is a joined current snapshot, leader-slot totals can differ slightly from the protocol epoch total when scheduled identities are no longer present in the current validator set.

How operators use it

Validator operators use leader-slot context to plan monitoring and incident response. Application teams use it to understand why distance to Solana leaders changes over time and why one fixed city is not enough for every slot.