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

https://opbnb-testnet.nodereal.io/v1/64a9df0874fb4a93b9d0a3849de012d3

opBNB Testnetevmnodereal.io· opbnb-testnetcompare ↔
Posture score
78
Speed score
68
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
73d
Session resumed
yes
TLS handshake
450ms
Resumption
285ms
TTFB
911ms
RPC block height
211,233,178
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake450ms
Resumed?yes · 285ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectnodereal.io
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANsnodereal.io, *.nodereal.io
Not before2025-11-23
Not after2026-12-22
Days to expiry73d
Chain SHA-25606a4e54c2dad4df0…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
D68
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://opbnb-testnet.nodereal.io/v1/64a9df0874fb4a93b9d0a3849de012d3
Host
Chain ID
5611
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-10T07:33:40.510928626Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
62ms
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://opbnb-testnet.nodereal.io/v1/64a9df0874fb4a93b9d0a3849de012d3' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:43:26.057Z
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.