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

https://node1.bityuan.com/eth

BitYuan Mainnetevmbityuan.com· node1compare ↔
Posture score
78
Speed score
56
TLS version
TLS 1.2
Cipher
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
64d
Session resumed
yes
TLS handshake
389ms
Resumption
189ms
TTFB
1.47s
RPC block height
47,764,028
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake389ms
Resumed?yes · 189ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectnode1.bityuan.com
IssuerZeroSSL ECC DV SSL CA 2
Key typeECDSA-P-256
Chain length3
SANsnode1.bityuan.com
Not before2026-09-13
Not after2026-12-12
Days to expiry64d
Chain SHA-25666cf627b61650988…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
F56
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://node1.bityuan.com/eth
Host
Chain ID
2999
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_ECDSA_WITH_AES_256_GCM_SHA384
Last seen
2026-10-09T13:08:29.283852917Z
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://node1.bityuan.com/eth' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:57:32.263Z
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.