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

wss://opbnb-mainnet.nodereal.io/ws/v1/e9a36765eb8a40b9bd12e680a1fd2bc5

opBNB Mainnetevmnodereal.io· opbnb-mainnetcompare ↔
Posture score
61
Speed score
100
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
100d
Session resumed
no
TLS handshake
28ms
Resumption
22ms
TTFB
64ms
RPC block height
-
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake28ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.nodereal.io
IssuerAmazon RSA 2048 M01
Key typeRSA-2048
Chain length3
SANs*.nodereal.io
Not before2026-07-05
Not after2027-01-18
Days to expiry100d
Chain SHA-2564168406c215e5f13…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D61
Speed
A+100
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
wss://opbnb-mainnet.nodereal.io/ws/v1/e9a36765eb8a40b9bd12e680a1fd2bc5
Host
Chain ID
204
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_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-10T10:07:47.735304078Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
828ms
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 'wss://opbnb-mainnet.nodereal.io/ws/v1/e9a36765eb8a40b9bd12e680a1fd2bc5' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T14:06:58.433Z
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.