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

https://evm.exsat.network

exSat Mainnetevmexsat.network· evmcompare ↔● fastest right now● PQ hybrid
Posture score
96
Speed score
94
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
http/1.1
Cert expires in
110d
Session resumed
yes
TLS handshake
70ms
Resumption
67ms
TTFB
843ms
RPC block height
63,152,046
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNhttp/1.1
PQ classPQ hybrid
Handshake70ms
Resumed?yes · 67ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.exsat.network
IssuerAlibaba Cloud GCC R46 AlphaSSL CA 2025
Key typeRSA-2048
Chain length3
SANs*.exsat.network, exsat.network
Not before2025-12-28
Not after2027-01-29
Days to expiry110d
Chain SHA-256f98218b60d401dd9…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
A+96
Speed
A94
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://evm.exsat.network
Host
Chain ID
7200
VM
evm
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T06:08:46.341635917Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
843ms
Latest block height
-
Current fastest URL
https://evm.exsat.network
Using this RPCtabs auto-fill the URL + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://evm.exsat.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:40:20.636Z
SHA-256 of canonical content
computed in your browser
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.