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

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

BC Hyper Chain Mainnetevmbchscan.io· datahub-asia02compare ↔● fastest right now
Posture score
83
Speed score
63
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
81d
Session resumed
yes
TLS handshake
264ms
Resumption
236ms
TTFB
1.27s
RPC block height
15,608,609
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake264ms
Resumed?yes · 236ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectdatahub-asia02.bchscan.io
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsdatahub-asia02.bchscan.io
Not before2026-09-30
Not after2026-12-29
Days to expiry81d
Chain SHA-2561366d437eec5d6ec…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
D63
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://datahub-asia02.bchscan.io/
Host
Chain ID
3030
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_AES_128_GCM_SHA256
Last seen
2026-10-09T13:08:29.55175507Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
1.27s
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://datahub-asia02.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:16.933Z
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.