wss://ws-rpc.mainnet.lukso.network

LUKSO Mainnetevm

lukso.network· ws-rpc.mainnet compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

66d

Session resumed

yes

TLS handshake

371ms

Resumption

144ms

TTFB

2.23s

RPC block height

8,542,577

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake371ms

Resumed?yes · 144ms

OCSP stapledno

SCTs presentno

Certificate chain

Subject*.mainnet.lukso.network

IssuerYR1

Key typeRSA-2048

Chain length3

SANs*.consensus.mainnet.lukso.network, *.europe-west4.mainnet.lukso.network, *.execution.mainnet.lukso.network +3

Not before2026-09-16

Not after2026-12-15

Days to expiry66d

Chain SHA-256f62217f5ed5e3618…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

F36

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

wss://ws-rpc.mainnet.lukso.network

Host

ws-rpc.mainnet.lukso.network

Chain

LUKSO Mainnet

Chain ID

evm

Platform type

chain

Sibling RPCs

view all on chain page →

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-09T21:17:34.078874081Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

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 'wss://ws-rpc.mainnet.lukso.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T05:52:46.878Z

SHA-256 of canonical content

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.