https://go.getblock.io/cc778cdbdf5c4b028ec9456e0e6c0cf3

BNB Smart Chain Mainnetevm

getblock.io· go 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

84d

Session resumed

TLS handshake

184ms

Resumption

193ms

TTFB

1.29s

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake184ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subject*.getblock.io

IssuerYR1

Key typeRSA-2048

Chain length3

SANs*.getblock.io

Not before2026-10-02

Not after2026-12-31

Days to expiry84d

Chain SHA-256002fc28a53c0cd97…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

D66

Speed

D60

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://go.getblock.io/cc778cdbdf5c4b028ec9456e0e6c0cf3

Host

go.getblock.io

Chain

BNB Smart Chain 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-07T23:57:35.14068561Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

649ms

Latest block height

Current fastest URL

https://bsc.blockrazor.xyz/fullprivacy

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://go.getblock.io/cc778cdbdf5c4b028ec9456e0e6c0cf3' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T06:55:42.081Z

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.