Solana speed, measured: slot time and real transactions per second
Measured slot time against the 200 ms target, user transactions per second, the share of slots skipped this epoch, and how far finality trails the newest slot. Read from the network every run; daily history kept.
Solana produced a slot every 215 ms on average over the 12 hours to 2026-11-16 00:42 UTC, against a 200 ms target, and carried 1,708 user transactions a second (read from getRecentPerformanceSamples).
- Measured slot time
- 214.9 ms
- 12.0 h window; target 200 ms
- Slower than target by
- 7.5%
- User transactions a second
- 1,708
- mean over the window
- Busiest minute
- 2,923 a second
- Slowest minute, slot time
- 223 ms
- Vote transactions in the samples
- 0.0%
- votes left the chain with Alpenglow
- Slots skipped this epoch
- 0.02%
- 82 of 350,780 leader slots
- Finality trails the newest slot by
- 0 slots
- readings 0, 1, 0
The table
12 rows, 4 columns. Click a column heading to sort. The plain-English explanation is on its page.
| Measure | Value | Unit | Read or computed |
|---|---|---|---|
| Mean slot time | 214.9 | ms | computed from samples |
| Median 1-minute slot time | 215.1 | ms | computed from samples |
| Slowest 1-minute slot time | 223 | ms | computed from samples |
| Slot-time target | 200 | ms | protocol (SIMD-0525) |
| User transactions per second, mean | 1,708 | tx/s | computed from samples |
| User transactions per second, busiest minute | 2,923 | tx/s | computed from samples |
| User transactions per second, quietest minute | 921 | tx/s | computed from samples |
| All transactions per second, mean | 1,708 | tx/s | computed from samples |
| Vote transactions in samples | 0 | % | computed from samples |
| Slots skipped, epoch so far | 0.02 | % | read (getBlockProduction) |
| Finality lag | 0 | slots | read (getSlot) |
| Sample window | 12 | hours | read |
Showing all 12 rows. Full table as CSV
History
7 readings kept in the file, newest first.
| Date | Epoch | Slot time (ms) | User tx a second | Vote share (%) | Skipped (%) | Finality lag (slots) |
|---|---|---|---|---|---|---|
| 2026-11-16 | 1087 | 214.9 | 1,708 | 0 | 0.02 | 0 |
| 2026-11-15 | 1086 | 215.1 | 2,006 | 0 | 0.03 | 0 |
| 2026-11-14 | 1085 | 215.4 | 2,046 | 0 | 0.09 | 0 |
| 2026-11-13 | 1085 | 215.2 | 2,101 | 0 | 0.14 | 0 |
| 2026-11-12 | 1084 | 215 | 2,221 | 0 | 0.11 | 0 |
| 2026-11-11 | 1083 | 214.9 | 1,792 | 0 | 0.22 | 0 |
| 2026-11-10 | 1083 | 214.2 | 2,008 | 0 | 0.71 | 0 |
Showing all 7 readings. Full history in the JSON
How this is measured
Slot time = total sample seconds × 1,000 ÷ total slots over the window. Transactions per second = non-vote transactions ÷ sample seconds (the same as all transactions since Alpenglow moved votes off-chain). Worst and best minute are the 1-minute samples with the slowest slot time and the highest throughput. Skipped share = (leader slots − blocks produced) ÷ leader slots for the current epoch so far. Finality lag = processed slot − finalized slot, median of three back-to-back readings.
What would make it wrong
- Samples come from one RPC node's view of the network and cover at most the last 12 hours; a gap between runs is not seen.
- Throughput is what users sent, not what the network can carry. Most Solana traffic is automated trading, and about a third of landed transactions fail (they still count here).
- The two getSlot calls are not atomic, so finality lag can read one slot high or low.
- Skipped share is for the epoch so far, which can be only a few hours.
Sources
- solana.com /docs/rpc/http/getrecentperformancesamples
- solana.com /docs/rpc/http/getblockproduction
- solana.com /upgrades/reduced-slot-times
- solana.com /upgrades/alpenglow
Every number here is read (from the network or a public API, at the time shown), computed from reads by the formula above, or stated by its source; the methodology page explains the three. SolPilled is independent and unofficial, not the Solana Foundation. Nothing here is financial advice.
Cite or reuse this data
Free to reuse with attribution under CC BY 4.0. Machine-readable: /data/network-speed.json (everything, including history and the method) and /data/network-speed.csv (the table). Agents can also read it through our MCP server.
Suggested citation:
SolPilled, "Solana speed, measured: slot time and real transactions per second", https://solpilled.com/data/network-speed/ (data as of 2026-11-16T00:42:46.855Z). CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/), attribute SolPilled (solpilled.com). More Solana data
- Exit cost of Solana staking tokens by size
- The SOL holder ledger: what each way of holding SOL pays
- Bridging USDC to Solana: what $100, $1,000 and $10,000 land as
- Solana account deposits (rent-exempt minimums), read live
- Solana transaction fees, sampled from recent blocks
- Where Solana fees go: apps, the chain itself and Jito tips, 30 days
- Solana epoch length, measured
- Solana incidents: the official status page record, and what we measure
- Solana protocol changes, 2025 to 2026, dated from the chain
- Solana supply, inflation and staked share
- Solana validators: stake concentration and client mix
- The Solana ecosystem by category
- Solana's headline numbers, one reading a day