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

https://lite.chain.opentensor.ai

Subtensor EVMevmopentensor.ai· lite.chaincompare ↔
Posture score
83
Speed score
85
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
70d
Session resumed
yes
TLS handshake
127ms
Resumption
137ms
TTFB
685ms
RPC block height
9,234,577
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake127ms
Resumed?yes · 137ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectlite-edge.chain.opentensor.ai
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANsentrypoint-finney.opentensor.ai, lite-edge.chain.opentensor.ai, lite.chain.opentensor.ai
Not before2026-09-18
Not after2026-12-17
Days to expiry70d
Chain SHA-256c4c97b60e8b42c36…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
B85
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://lite.chain.opentensor.ai
Host
Chain ID
964
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-07T23:58:01.837498902Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
465ms
Latest block height
-
Current fastest URL
https://rpc.blockmachine.io
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://lite.chain.opentensor.ai' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:41:30.355Z
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.