https://datahub-asia01.bchscan.io

BC Hyper Chain Mainnetevm

bchscan.io· datahub-asia01 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

41d

Session resumed

yes

TLS handshake

434ms

Resumption

202ms

TTFB

1.40s

RPC block height

15,608,609

TLS handshake

VersionTLS 1.2

CipherTLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

KEX groupclassical

ALPNhttp/1.1

PQ classClassical only

Handshake434ms

Resumed?yes · 202ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectdatahub-asia01.bchscan.io

IssuerYR2

Key typeRSA-2048

Chain length3

SANsdatahub-asia01.bchscan.io

Not before2026-08-22

Not after2026-11-20

Days to expiry41d

Chain SHA-256edacae0309bb770f…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

F54

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://datahub-asia01.bchscan.io

Host

datahub-asia01.bchscan.io

Chain

BC Hyper Chain Mainnet

Chain ID

3030

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-09T13:08:29.539408242Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

1.27s

Latest block height

Current fastest URL

https://datahub-asia02.bchscan.io/

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

Scan reportschema rpcscan-report · captured 2026-10-10T06:45:00.031Z

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.