Every Solana wallet, DEX, and application communicates with the blockchain through RPC (Remote Procedure Call) nodes. When Solana is congested and your transactions fail or slow down, the RPC node is often the bottleneck. Here's what you need to know.
What Is an RPC Node?
An RPC node is a Solana full node that exposes an API for querying blockchain state and submitting transactions. When you swap on Jupiter or check your wallet balance in Phantom, a request goes to an RPC node that reads from the blockchain and returns data.
You never interact with RPC directly — your wallet or app handles it. But the quality of the RPC node determines:
- How fast your transaction confirmations appear
- Whether your transactions land during network congestion
- How accurate your balance and price data is
Public vs. Private RPC
Public RPC (api.mainnet-beta.solana.com) — Free, run by Solana Labs. Heavily rate-limited. During periods of high network activity, transactions submitted via public RPC often fail or take much longer.
Private RPC — Paid endpoints from specialized providers. Faster, dedicated infrastructure, higher rate limits, and often MEV-protection features.
Major Solana RPC Providers in 2026
| Provider | Free Tier | Paid Tier | Notable Features | |----------|-----------|-----------|-----------------| | Helius | 100 req/s | From $49/mo | MEV protection (Shield), webhooks | | QuickNode | Limited | From $49/mo | Multi-chain, fast geographic routing | | Alchemy | Limited | From $49/mo | Analytics dashboard, archive data | | Triton | None | Enterprise | Used by major protocols |
For most retail users, Phantom wallet and Jupiter use their own optimized RPC infrastructure — you benefit from this without configuring anything.
When Does RPC Quality Matter?
For casual users (occasional swaps, portfolio checking): public RPC or wallet defaults are fine. The difference is negligible.
For active DeFi users (frequent swaps, LP management, arbitrage): a private RPC endpoint noticeably improves transaction landing rate during congestion.
For bot/programmatic users: private RPC with high throughput limits is essential. Bots submitting hundreds of transactions per minute will be rate-limited to uselessness on public endpoints.
Helius Shield: MEV Protection via RPC
Helius Shield is a special transaction submission endpoint that routes transactions directly to validators, bypassing the public mempool. This prevents frontrunning bots from seeing your transactions before they're included.
For large swaps ($10,000+) on Solana, using a MEV-protected RPC can save meaningful amounts. For small swaps, the difference is negligible.
Configuring a Custom RPC in Phantom
Phantom wallet lets you set a custom RPC endpoint:
- Settings → Developer Settings → Custom RPC
- Paste your provider's Mainnet RPC URL
- Save and reconnect
This routes all your Phantom transactions through your chosen provider instead of the default.
RPC and DApp Connections
When you use Jupiter, SovereignSwap, or other Solana DApps, the DApp itself has an RPC endpoint configured for reading chain data. Your wallet uses a separate RPC for submitting transactions.
For most users, the wallet RPC matters more — that's what actually sends your transactions to the network.