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

wss://rpc.heima-parachain.heima.network

Heimaevmheima.network· rpc.heima-parachaincompare ↔
Posture score
73
Speed score
78
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
-
PQ class
Unknown
ALPN
http/1.1
Cert expires in
40d
Session resumed
yes
TLS handshake
136ms
Resumption
112ms
TTFB
566ms
RPC block height
11,197,363
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX group-
ALPNhttp/1.1
PQ classUnknown
Handshake136ms
Resumed?yes · 112ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc.heima-parachain.heima.network
IssuerYR2
Key typeRSA-2048
Chain length3
SANsrpc.heima-parachain.heima.network
Not before2026-08-21
Not after2026-11-19
Days to expiry40d
Chain SHA-256c6453966ba6a2f63…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
C78
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
wss://rpc.heima-parachain.heima.network
Host
Chain
Chain ID
212013
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
Unknown
Key exchange
-
Cipher
TLS_AES_256_GCM_SHA384
Last seen
2026-10-10T05:59:09.914072084Z
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 + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'wss://rpc.heima-parachain.heima.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:00:25.392Z
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.