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

https://rpc.xlayer.tech

X Layer Mainnetevmxlayer.tech· rpccompare ↔● PQ hybrid
Posture score
97
Speed score
68
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
103d
Session resumed
yes
TLS handshake
149ms
Resumption
80ms
TTFB
993ms
RPC block height
72,648,427
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake149ms
Resumed?yes · 80ms
OCSP stapledyes
SCTs presentno
Certificate chain
Subject*.xlayer.tech
IssuerGeoTrust TLS RSA CA G1
Key typeRSA-2048
Chain length2
SANs*.xlayer.tech, xlayer.tech
Not before2026-01-19
Not after2027-01-18
Days to expiry103d
Chain SHA-256f5a75157f3ce02bd…
Misconfigurations
● No issues detected.
Grades
Posture
A+97
Speed
D68
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://rpc.xlayer.tech
Host
Chain ID
196
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:43.014677156Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
887ms
Latest block height
-
Current fastest URL
https://xlayer.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://rpc.xlayer.tech' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:50:10.821Z
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.