RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://mainnetbeta-rpc.eclipse.xyz

Solanasolanaeclipse.xyz· mainnetbeta-rpccompare ↔
Posture score
83
Speed score
89
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
36d
Session resumed
yes
TLS handshake
102ms
Resumption
82ms
TTFB
649ms
RPC block height
193,703,041
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake102ms
Resumed?yes · 82ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectmainnetbeta-rpc.eclipse.xyz
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANs*.eclipserpc.xyz, mainnetbeta-rpc.eclipse.xyz
Not before2026-08-17
Not after2026-11-15
Days to expiry36d
Chain SHA-2564489a39b2cbaa0c5…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
B89
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://mainnetbeta-rpc.eclipse.xyz
Host
Chain
Chain ID
-
VM
solana
Platform type
chain
Live probe (last 24 h)
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
TLS posture (post-quantum)full history →
Class
Classical only
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T05:44:25.594088806Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
Using this RPCtabs auto-fill the URL
Solana JSON-RPC: getHealth and getSlot.
curl -X POST 'https://mainnetbeta-rpc.eclipse.xyz' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"getSlot","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:48:01.296Z
SHA-256 of canonical content
computing…

The hash covers every field above the JSON serialization with sorted keys. Re-running this computation against the downloaded artifact must produce the same hash; that's how RPCScan's future on-chain proofs (rpcscanchain) will let anyone verify a published snapshot wasn't tampered with.