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 Sep 19, 2026, 08:03 AM UTC

Schedule epoch

1,037

Leader slots

430,604slots

Leader validators

661validators

96.1%

Top leader

17,404slots

Figment

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

17,404 slots

Helius

3.7%

15,900 slots

binance staking

2.8%

11,968 slots

Jupiter

2.7%

11,412 slots

Bitwise Onchain Solutions

2.2%

9,648 slots

Ledger by Figment

2.1%

9,052 slots

Kraken 2

2.1%

8,844 slots

Galaxy

1.6%

7,056 slots

Everstake

1.6%

7,040 slots

Staking Facilities | MEV 🔥

1.5%

6,420 slots

Top countries by leader slots

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

Germany

170 validators · 34.1%

146,796 slots

Netherlands

118 validators · 20%

86,156 slots

United States

120 validators · 15.3%

65,744 slots

United Kingdom

33 validators · 8.5%

36,776 slots

Japan

54 validators · 5.5%

23,828 slots

Lithuania

16 validators · 4.5%

19,192 slots

Singapore

47 validators · 4.3%

18,412 slots

Ireland

7 validators · 2%

8,668 slots

Sweden

10 validators · 1.9%

8,080 slots

Canada

11 validators · 0.7%

2,960 slots

France

11 validators · 0.6%

2,500 slots

Hong Kong SAR China

13 validators · 0.5%

2,188 slots

Switzerland

1 validators · 0.4%

1,872 slots

Brazil

13 validators · 0.3%

1,308 slots

South Korea

1 validators · 0.3%

1,152 slots

Top cities by leader slots

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

Frankfurt am Main

106 validators · 28.5%

122,824 slots

Amsterdam

75 validators · 13.7%

59,000 slots

London

26 validators · 8.1%

34,804 slots

Tokyo

47 validators · 4.9%

21,092 slots

Lelystad

24 validators · 4.7%

20,052 slots

Šiauliai

16 validators · 4.5%

19,192 slots

Singapore

47 validators · 4.3%

18,412 slots

New York City

19 validators · 3.7%

15,832 slots

Ashburn

3 validators · 2.9%

12,336 slots

Eschborn

31 validators · 2.4%

10,328 slots

Offenbach

28 validators · 2.2%

9,600 slots

Stockholm

10 validators · 1.9%

8,080 slots

Newark

9 validators · 1.7%

7,456 slots

Boardman

1 validators · 1.3%

5,692 slots

Chicago

22 validators · 1.2%

5,240 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.