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 Jul 22, 2026, 06:07 AM UTC

Schedule epoch

1,005

Leader slots

431,996slots

Leader validators

689validators

96.4%

Top leader

16,500slots

Helius

3.8%

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.

Helius

3.8%

16,500 slots

Figment

3.7%

16,144 slots

Jupiter

2.9%

12,636 slots

binance staking

2.8%

12,164 slots

Ledger by Figment

2.2%

9,492 slots

Bitwise Onchain Solutions

1.9%

8,272 slots

Everstake

1.7%

7,464 slots

Galaxy

1.7%

7,192 slots

Kraken 2

1.6%

7,040 slots

Staking Facilities | MEV 🔥

1.6%

6,908 slots

Top countries by leader slots

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

Germany

161 validators · 26.7%

115,368 slots

Netherlands

110 validators · 19.4%

83,908 slots

United States

132 validators · 15.4%

66,672 slots

United Kingdom

34 validators · 11.8%

50,924 slots

Japan

65 validators · 5.6%

24,220 slots

Lithuania

15 validators · 4.6%

19,952 slots

Canada

16 validators · 4.6%

19,876 slots

Singapore

51 validators · 4.6%

19,836 slots

Sweden

11 validators · 1.9%

8,040 slots

Ireland

7 validators · 1.3%

5,640 slots

Hong Kong SAR China

18 validators · 0.6%

2,568 slots

Brazil

16 validators · 0.6%

2,504 slots

Switzerland

1 validators · 0.5%

2,048 slots

France

12 validators · 0.4%

1,940 slots

Czechia

3 validators · 0.3%

1,320 slots

Top cities by leader slots

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

Frankfurt am Main

101 validators · 21.2%

91,504 slots

Amsterdam

65 validators · 14.4%

62,280 slots

London

26 validators · 11.5%

49,552 slots

Šiauliai

15 validators · 4.6%

19,952 slots

Singapore

51 validators · 4.6%

19,836 slots

Lelystad

27 validators · 4.1%

17,776 slots

Toronto

10 validators · 4%

17,320 slots

Ashburn

6 validators · 3%

12,864 slots

Los Angeles

23 validators · 2.8%

12,208 slots

Offenbach

30 validators · 2.4%

10,164 slots

New York City

15 validators · 2.4%

10,156 slots

Eschborn

24 validators · 2.1%

9,080 slots

Ebara

8 validators · 2%

8,692 slots

Stockholm

11 validators · 1.9%

8,040 slots

Tokyo

51 validators · 1.8%

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