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

https://coinbit-rpc-mainnet.chain.sbcrypto.app

Coinbit Mainnetevmsbcrypto.app· coinbit-rpc-mainnet.chaincompare ↔● fastest right now
Posture score
78
Speed score
26
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
99d
Session resumed
yes
TLS handshake
858ms
Resumption
373ms
TTFB
2.64s
RPC block height
53,991,106
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake858ms
Resumed?yes · 373ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.chain.sbcrypto.app
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANs*.chain.sbcrypto.app
Not before2025-12-16
Not after2027-01-14
Days to expiry99d
Chain SHA-25620982ba24879eb62…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
F26
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://coinbit-rpc-mainnet.chain.sbcrypto.app
Host
Chain ID
112
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_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-07T23:57:38.675279259Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
2.64s
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://coinbit-rpc-mainnet.chain.sbcrypto.app' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T11:30:27.703Z
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.