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

https://api.elastos.io/eco

ECO Mainnetevmelastos.io· apicompare ↔● fastest right now● PQ hybrid
Posture score
78
Speed score
93
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
56d
Session resumed
yes
TLS handshake
11ms
Resumption
11ms
TTFB
472ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake11ms
Resumed?yes · 11ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectelastos.io
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANselastos.io, *.elastos.io
Not before2026-09-06
Not after2026-12-05
Days to expiry56d
Chain SHA-256f35fdf25b5db1c74…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
A93
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
30
Endpoint identity
URL
https://api.elastos.io/eco
Host
Chain ID
12343
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:39:06.3859246Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
-
Latest block height
-
Current fastest URL
https://api.elastos.io/eco
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://api.elastos.io/eco' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:40:53.549Z
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.