Why TPS Tracking Matters for Solana Traders
On Solana, transactions per second (TPS) is not just a vanity metric – it directly affects whether your swaps land, how much priority fee you pay, and how aggressive you need to be with slippage.
Solana has demonstrated very high real-world throughput, including:
- Peaks above 100,000 TPS in on-chain stress tests that included vote transactions.
- Sustained non-vote (user) throughput around 800–1,500 TPS in busy periods.
These numbers come from independent measurements and explorer data, and they highlight a key point: headline TPS and actual user TPS are not the same thing. (decrypt.co)
PumpView adds a trader-focused layer on top of this reality by exposing a live TPS chart directly in the trading interface. This article explains what that chart is really showing, how it relates to Solana’s underlying metrics, and how to use it to make better trading decisions.
Quick Refresher: How TPS Is Measured on Solana
Before explaining PumpView’s TPS tracking, it’s important to understand how Solana TPS is usually reported.
Vote vs non-vote TPS
Solana processes two broad categories of transactions:
- Vote transactions – validator messages used to maintain consensus.
- Non-vote (user) transactions – swaps, mints, transfers, DEX interactions, etc.
Many public metrics lump both together, which inflates the apparent throughput. Explorers like Solscan explicitly distinguish between:
- Standard TPS – all transactions, including votes.
- “True” or non-vote TPS – user-facing transactions only.
Analyses of mainnet performance show that vote traffic can be 60–80% of total TPS, meaning the user portion is typically a minority of the raw number you see quoted. (ccn.com)
For traders, non-vote TPS is what really matters, because that’s the capacity your swaps compete for.
Real-world throughput vs theoretical peak
You’ll often see:
- Theoretical peak: tens of thousands of TPS or more, based on hardware and protocol design.
- Stress-test peaks: >100,000 TPS on mainnet under synthetic load that includes vote transactions and simple program calls.
- Observed user TPS: typically in the hundreds to low thousands of non-vote TPS during active periods.
Independent measurements and reports have shown:
- Non-vote TPS baselines in the high hundreds to low thousands in busy months.
- Daily records of over 100 million non-vote transactions, averaging over 1,000 non-vote TPS across a week. (kucoin.com)
The key takeaway: TPS is highly dynamic, and what you experience as a trader depends on the current non-vote load and congestion on specific programs (Raydium, Meteora, pump.fun, etc.), not just the global headline number.
What PumpView’s TPS Chart Is Actually Showing
PumpView is a real-time Solana DEX trade scanner. One of its core UI elements is a live Solana TPS chart that updates alongside:
- The live trade stream (PumpSwap, Raydium, Meteora, and other DEXes)
- Hot Tokens & Early Scanner
- Wash trading metrics and custom signals
Data source and perspective
PumpView’s TPS chart is network-wide, not limited to trades it sees. It reflects:
- The current Solana mainnet TPS, as reported by standard network metrics (including vote + non-vote), over a short rolling window.
Because the raw network metric includes vote transactions, the number you see on PumpView’s TPS chart will usually be higher than the effective user TPS you feel when trading. That’s expected and consistent with how most explorers and monitoring tools report TPS. (ccn.com)
Why PumpView still shows total TPS (not just non-vote)
Even though non-vote TPS is the more precise measure of user capacity, PumpView’s choice to show the headline TPS is still very useful for traders:
- It’s the most widely available, low-latency metric from Solana’s public infrastructure.
- Spikes and drops in total TPS correlate strongly with trader experience – when the network is slammed by bots or heavy activity, both vote and non-vote throughput move together.
- It’s easy to interpret in context: you don’t need exact non-vote numbers to know that 400 vs 3,000 TPS implies very different congestion regimes.
PumpView’s goal is not to be a protocol research tool; it’s to give traders a fast, intuitive signal about current network conditions.
How to Read PumpView TPS in a Trading Context
1. Low-to-moderate TPS: easier fills, lower priority fees
When PumpView’s TPS chart is in a lower band relative to recent history (for example, well below the peaks you’ve seen in the last few days):
- DEX swaps are more likely to land with modest or even zero priority fees.
- You can often tighten slippage on memecoins without constant failures.
- Bots are less competitive on priority fee auctions, so manual traders have a fairer shot.
This is typically when you can:
- Use standard wallet defaults for priority fees.
- Run more conservative stop-loss and take-profit orders without worrying they’ll be skipped due to underbidding on compute price.
2. Elevated TPS: active markets, rising competition
When the TPS line is elevated but not spiking, you’re in a regime where:
- User activity is high – more swaps, more bots, more arbitrage.
- Priority fees start to matter for time-sensitive trades.
- Latency-sensitive strategies (sniping new launches, tight scalps) need more careful settings.
In this zone, consider:
- Bumping priority fee slightly above wallet defaults for critical entries/exits.
- Using aggregators like Jupiter to route around congested pools when possible.
- Watching PumpView’s live trade stream to see whether other traders’ swaps are landing quickly or stalling.
Independent fee data has shown that during heavy activity, priority fees dominate total costs on Solana, with base fees remaining tiny (5,000 lamports per signature) and burned, while priority fees are split between validators and burn. (solanafloor.com)
3. TPS spikes: congestion, failed or dropped transactions
When PumpView’s TPS chart shows sharp spikes, especially if they coincide with:
- A hot token launch
- A major airdrop claim
- A market-wide volatility event
…you’re likely in a congested regime where:
- Non-vote TPS is near its current practical ceiling for the programs you’re using.
- Priority fees can jump by orders of magnitude for inclusion in the next few blocks.
- Dropped or failed transactions increase, especially for low-fee or poorly configured wallets.
Historical episodes (e.g., high-profile memecoin launches and airdrops) have shown:
- User TPS in the thousands, with many users reporting failures if they didn’t set adequate priority fees.
- Priority fees reaching levels far above normal, while base fees stayed constant. (solanafloor.com)
In these conditions, PumpView’s TPS chart is effectively a warning light:
- If you see a vertical spike, assume you’re competing with bots and high-fee flows.
- Reassess whether you really need to trade right now, or whether you can wait for the TPS to cool off.
Practical Ways to Use PumpView TPS While Trading
1. Timing entries and exits on volatile memecoins
For memecoins on PumpSwap, Raydium, or Meteora:
- Before entering a position:
- Check PumpView’s TPS chart.
- If TPS is already elevated and climbing, expect:
- Higher slippage requirements
- The need for higher priority fees
- More competition from bots
- When exiting:
- If TPS is spiking, consider:
- Increasing priority fee to ensure your exit lands.
- Widening slippage slightly if you must exit immediately.
If TPS is low and stable, you can often trade more patiently and avoid overpaying for priority.
2. Adjusting custom signal strategies
PumpView lets you define custom signal strategies with alerts (for example, based on buy/sell flow, wash trading filters, or Hot Tokens scores). TPS adds an important dimension:
- When TPS is low:
- Signals based on volume or trade count may be more reliable, as each trade is less likely to be dropped or delayed.
- When TPS is high or spiking:
- Consider that some signals may be distorted by failed or delayed transactions.
- You might want to raise thresholds (e.g., require more sustained buy volume) before acting on a signal.
In other words, TPS is context for your signals: the same pattern of buys/sells means something different in a calm network vs a congested one.
3. Interpreting wash trading and fake volume
PumpView includes a wash trading detection score for tokens. TPS helps you interpret that score:
- If a token shows high wash score (suggesting fake or circular volume) while network TPS is low, it’s more likely that:
- The suspicious activity is localized to that token.
- If network TPS is very high and many tokens are active, some noisy patterns may simply reflect broad market activity.
By glancing at TPS, you avoid overreacting to wash-score spikes that occur during chain-wide frenzies.
4. Choosing when to deploy new capital
If you’re planning to:
- Move fresh SOL into your trading wallet
- Bridge into Solana from another chain
- Deploy a new strategy that requires many on-chain actions
…PumpView’s TPS chart can help you avoid deploying into peak congestion. Waiting for TPS to normalize can mean:
- Lower cumulative priority fees across multiple transactions
- Fewer failed attempts when setting up positions or LPs
Limitations and What TPS Can’t Tell You
PumpView’s TPS chart is powerful, but it’s important to understand what it does not capture directly:
- Per-program congestion
- Solana’s runtime can be bottlenecked on specific programs (e.g., a popular DEX or token program) even if global TPS looks moderate.
-
A token on a heavily used AMM pool can experience congestion even when the overall network seems fine.
-
Your specific RPC or wallet issues
-
High TPS might correlate with more RPC timeouts, but a bad endpoint or wallet bug can cause issues even at low TPS.
-
Exact non-vote TPS
- PumpView’s chart is based on the headline network TPS, not a separate non-vote-only metric.
- For research-level detail, you’d still use explorers and analytics tools that break out vote vs non-vote.
Use TPS as a macro signal, not a precise engineering metric.
Complementary Tools for Deeper TPS Insight
To go beyond PumpView’s trader-focused TPS view, you can cross-check with:
- Solscan – shows both standard TPS and “true” TPS (non-vote), plus per-program stats. (ccn.com)
- Helius / other RPC dashboards – many providers expose real-time performance metrics and logs.
- Validator and analytics dashboards – community tools often chart vote vs non-vote ratios and historical peaks.
PumpView’s strength is combining TPS with live trades, token scores, and alerts in one place. External tools give you extra depth if you want to understand the protocol-level behavior behind what you’re seeing.
Putting It All Together
For active Solana traders, especially in memecoins and DEX markets, TPS is not an abstract number – it’s a live indicator of how hard you need to fight to get into the next block.
PumpView’s TPS tracking helps you:
- See network pressure in real time alongside your trading feed.
- Decide when to trade aggressively with higher priority fees and wider slippage.
- Know when to stand back during extreme spikes and wait for better conditions.
- Interpret your own signals and wash-trading scores in the right network context.
Use PumpView’s TPS chart as your network weather radar: always visible, easy to interpret at a glance, and crucial for deciding whether it’s a good moment to fly—or whether you’re about to trade into a storm.