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

https://evm.cronos.org

Cronos Mainnetevmcronos.org· evmcompare ↔● PQ hybrid
Posture score
96
Speed score
61
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
80d
Session resumed
yes
TLS handshake
255ms
Resumption
136ms
TTFB
996ms
RPC block height
98,562,713
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake255ms
Resumed?yes · 136ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectcronos.org
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANscronos.org, *.testnet.zkevm.cronos.org, *.cronos.org +1
Not before2026-09-28
Not after2026-12-27
Days to expiry80d
Chain SHA-2560cf4dc8fe4f8e04a…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
A+96
Speed
D61
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://evm.cronos.org
Host
Chain ID
25
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-07T23:57:33.491090637Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
857ms
Latest block height
-
Current fastest URL
https://cronos.drpc.org
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.cronos.org' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:50:37.324Z
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.