PumpView/Blog
Solana TPS, Congestion, and Fees: A Practical Guide for Traders

Solana TPS, Congestion, and Fees: A Practical Guide for Traders

March 05, 2026solana
𝕏 Share on X 📣 Telegram

Solana TPS and Congestion: What Traders Actually Need to Know

If you trade actively on Solana, you’ve probably seen all three of these at some point:

This article cuts through the marketing numbers and explains, in trader language, how Solana TPS really works, what congestion looks like in practice, and how to reliably get your trades confirmed when the network is under stress.


TPS on Solana: Marketing vs. Reality

The headline numbers

Solana’s design target has long been tens of thousands of TPS. Early internal tests showed the network handling around 47,000 TPS without GPU acceleration. (solana.com) More recently, mainnet stress tests have pushed over 100,000 transactions per second in short bursts, making Solana the first major chain to cross six‑figure TPS on mainnet. (reddit.com)

Those numbers are capacity under stress, not what you see day‑to‑day when you’re trading.

Real-world throughput

Independent research looking at real, non‑vote transactions finds that sustained, real‑world TPS is much lower than the theoretical maximum. One 2025 study of blockchain payments data reports Solana’s highest recorded real TPS (excluding votes and failed transactions) at around 1,000 TPS. (public.bnbstatic.com)

That’s still orders of magnitude above most L1s, but it explains why:

As a trader, what matters isn’t the peak TPS screenshot — it’s how the network behaves when everyone is trying to hit the same program or pool as you.


What Counts as a “Transaction” on Solana?

When you look at TPS charts on explorers, remember:

Earlier community analyses pointed out that headline TPS often includes a large share of votes and non-user traffic, while “true TPS” for real user activity can be in the hundreds to low thousands. (reddit.com)

For traders, the key takeaway:

High TPS ≠ your swap will succeed. What matters is contention on the specific accounts and programs your transaction touches.


How Solana Fees Actually Work (And Why Congestion Hurts)

Solana’s fee model is critical to understanding congestion.

1. Base fee per signature

Solana has a fixed base fee of 5,000 lamports (0.000005 SOL) per signature. (docs.solxen.io) Most wallet transactions have one signature, so this part is tiny and predictable.

2. Compute Units (CU)

Every transaction consumes Compute Units (CU) — a measure of how much work it does. There is a global CU budget per block (around tens of millions of CU) and a per‑transaction CU limit. (docs.solxen.io) Complex swaps, routing across multiple DEXes, or on‑chain programs with heavy logic use more CU.

3. Priority fees in microlamports per CU

On top of the base fee, Solana supports optional priority fees:

Validators order transactions in their block queue by fee priority, so during congestion, transactions with higher priority fees are more likely to be included quickly. (solana.com)

Recent on‑chain data shows that during heavy activity (e.g., viral memecoin launches), priority fees dominate total transaction costs, making up well over 90% of fees paid, while the base fee remains negligible. (solanafloor.com)

For traders, this means:


Local Fee Markets and Why Only Some Things Get Congested

Solana introduced local (or localized) fee markets so that congestion is priced where it actually happens:

This is very different from Ethereum L1, where a single hyped mint can push gas prices up for everyone.

In practice, for Solana traders:

Tools like Jupiter (aggregator), Birdeye, and DexScreener help you see which pools are liquid and active. If one route is failing repeatedly, try:


What Congestion Actually Looks Like for Traders

From a trader’s perspective, Solana congestion typically shows up as:

Historically, congestion spikes have been driven by:

Even though the chain as a whole can handle very high TPS, a single hot program (like a mint or AMM pool) can become a bottleneck because everyone is trying to touch the same accounts in the same slots.


Stake-Weighted QoS, QUIC, and Why Your Connection Matters

To improve reliability under load, Solana has rolled out several networking and scheduling improvements over the last few years:

For end users, you don’t configure these directly, but they affect you indirectly via your RPC provider and wallet:

If you’re consistently seeing failures while others are trading fine, your RPC endpoint may be the bottleneck.


Practical Tips: Getting Trades Through During Congestion

1. Use explicit priority fees (not just wallet defaults)

On Solana, no priority fee often means no inclusion when things are hot.

There’s no universal “right number” because local fee markets are dynamic, but:

2. Reduce compute usage where possible

Because priority fees are per CU, reducing compute can lower your cost and make inclusion easier:

3. Avoid the most congested routes

With local fee markets, sometimes the best move is just use a different pool:

4. Be realistic about timing

During extreme events (viral mints, massive airdrops):

If you’re not competing for the very first blocks, it can be safer to wait for the initial spam wave to cool off before entering.

5. Monitor network health

Before doing size or leverage on Solana, it’s worth quickly checking:

If failure rates are elevated chain‑wide, consider:


How TPS and Congestion Change Trading Strategy

Understanding Solana’s TPS and congestion model should change how you trade:

Solana’s high TPS ceiling is a huge advantage, but it doesn’t remove the need to think about where and when you send transactions.


Key Takeaways for Solana Traders

If you treat TPS numbers as marketing and focus instead on local contention, priority fees, and route selection, you’ll have a much more realistic and profitable approach to trading on Solana.

𝕏 Share on X 📣 Telegram
Scan Solana Trades in Real Time
Track hot tokens, detect wash trading, and get signal alerts — free, no signup required.
Open PumpView.fun