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

https://explorer-rpc-http.mainnet.stages.humanode.io

Humanode Mainnetevmhumanode.io· explorer-rpc-http.mainnet.stagescompare ↔● fastest right now
Posture score
83
Speed score
93
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
36d
Session resumed
no
TLS handshake
94ms
Resumption
86ms
TTFB
475ms
RPC block height
20,184,688
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake94ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectexplorer-rpc-http.mainnet.stages.humanode.io
IssuerYR2
Key typeRSA-2048
Chain length3
SANsexplorer-rpc-http.mainnet.stages.humanode.io
Not before2026-08-17
Not after2026-11-15
Days to expiry36d
Chain SHA-256480ba9179aef57fd…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
A93
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://explorer-rpc-http.mainnet.stages.humanode.io
Host
Chain ID
5234
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
Classical only
Key exchange
-
Cipher
TLS_AES_256_GCM_SHA384
Last seen
2026-10-10T08:18:36.684275362Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
475ms
Latest block height
-
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://explorer-rpc-http.mainnet.stages.humanode.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T08:28:11.026Z
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.