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

https://rpc.testnet.lukso.network

LUKSO Testnetevmlukso.network· rpc.testnetcompare ↔● fastest right now
Posture score
83
Speed score
87
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
39d
Session resumed
yes
TLS handshake
98ms
Resumption
176ms
TTFB
570ms
RPC block height
8,703,249
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake98ms
Resumed?yes · 176ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.testnet.lukso.network
IssuerYR2
Key typeRSA-2048
Chain length3
SANs*.consensus.testnet.lukso.network, *.europe-west4.testnet.lukso.network, *.execution.testnet.lukso.network +2
Not before2026-08-20
Not after2026-11-18
Days to expiry39d
Chain SHA-256f2cecf7f0d9d1244…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
B87
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://rpc.testnet.lukso.network
Host
Chain ID
4201
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_128_GCM_SHA256
Last seen
2026-10-09T16:08:34.747617945Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
570ms
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://rpc.testnet.lukso.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:35:02.602Z
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.