https://rpc.bchscan.io

BC Hyper Chain Testnetevm

bchscan.io· rpc compare ↔

Posture score

Speed score

TLS version

TLS 1.2

Cipher

TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

KEX group

classical

PQ class

Classical only

ALPN

http/1.1

Cert expires in

39d

Session resumed

TLS handshake

438ms

Resumption

TTFB

1.35s

RPC block height

24,100,144

TLS handshake

VersionTLS 1.2

CipherTLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

KEX groupclassical

ALPNhttp/1.1

PQ classClassical only

Handshake438ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrpc.bchscan.io

IssuerYR1

Key typeRSA-2048

Chain length3

SANsrpc.bchscan.io

Not before2026-08-21

Not after2026-11-19

Days to expiry39d

Chain SHA-25662e7b2ae7f85b387…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

F53

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc.bchscan.io

Host

rpc.bchscan.io

Chain

BC Hyper Chain Testnet

Chain ID

6060

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_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

Last seen

2026-10-10T04:53:40.67036708Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:56:32.431Z

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.