Solana RPC Nodes & Endpoints

Solana public RPC endpoints

Free, third-party public endpoints for reads and prototyping. They are shared and rate-limited, not run by BLAZED.sh, so use a dedicated node for production traffic.

import { Connection } from "@solana/web3.js";

const connection = new Connection("https://api.mainnet-beta.solana.com", "confirmed");
const slot = await connection.getSlot();
console.log("Solana slot:", slot);

Dedicated Solana RPC node vs shared endpoints

Solana's public mainnet-beta endpoint is explicitly not meant for production, and it shows: getProgramAccounts scans over busy programs get rejected or truncated, websocket fan-out is capped, and rate limits arrive quickly. Serious Solana workloads, whether trading systems, indexers, or consumer apps at scale, outgrow shared RPC faster than on any EVM chain, because the chain moves at 400 millisecond slots and the common methods are heavier.

A dedicated Solana RPC node changes what is possible rather than just how fast: full getProgramAccounts scans, as many account and slot subscriptions as your architecture wants, and transaction submission that is not queued behind a public crowd. On BLAZED.sh the model will match our Ethereum product: your bot or indexer runs on the node host and reads over a local socket.

Solana RPC latency: architecture over benchmarks

With 400 millisecond slots, Solana punishes network distance more than any EVM chain: a public-internet round trip of tens to low hundreds of milliseconds can span multiple slots before your code reacts. Co-location is the structural answer. On our live Ethereum product, calls from the co-located container complete in under 10 milliseconds, and dedicated Solana RPC will apply the same architecture to the chain where the gap between local and remote is worth the most.

What a dedicated Solana node costs

BLAZED.sh prices node access in per-request credits granted monthly by your subscription, with a deliberately narrow weight spread: most RPC methods cost 1 credit, a few heavy operations like txpool_content and the trace_replay methods cost 4, and responses over 100KB add 50 credits per MB. The Beta plan is €75 per month with 1M credits, 1 container and 2 scripts; Beta XL is €249 per month with 5M credits, 3 containers and 4 scripts; Enterprise plans add private nodes and archive access. These are the live Ethereum plans today, and pricing is still being finalized. Dedicated Solana nodes will launch on the same credit model, with the waitlist above deciding rollout priority.

Solana's chatty method mix of constant polling and subscriptions is exactly where per-method weighted billing hurts most, and where a narrow credit spread keeps the forecast down to counting calls.

Perfect for

What is Solana?

Solana uses a single global state with parallel execution (Sealevel) and a proof-of-history clock to reach very high throughput and sub-second slot times. Its RPC surface differs entirely from Ethereum: methods like getSlot, getAccountInfo, getProgramAccounts, and sendTransaction, plus websocket account and slot subscriptions, and there is no EVM chain ID, so you select the cluster (mainnet-beta) by URL. Because block space is abundant but contention is real, the competitive edge for DEX trading, sniping, and market making comes from low-latency transaction submission and staked-connection priority. Heavy getProgramAccounts scans and websocket fan-out also strain public endpoints quickly, which is why serious Solana teams run dedicated RPC close to their bots and indexers.

Solana RPC: frequently asked questions