RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Decimal Smart Chain Mainnet

https://node.decimalchain.com/web3

Decimal Smart Chain Mainnetevmdecimalchain.com· nodecompare ↔
Posture score
78
Speed score
62
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
1d
Session resumed
yes
TLS handshake
196ms
Resumption
141ms
TTFB
1.16s
RPC block height
34,604,904
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake196ms
Resumed?yes · 141ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectdecimalchain.com
IssuerYR1
Key typeRSA-2048
Chain length3
SANs*.decimalchain.com, decimalchain.com
Not before2026-08-20
Not after2026-11-18
Days to expiry1d
Chain SHA-256d5f0b962d7c3cdf3…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsissue:comodoca.com · issue:digicert.com; cansignhttpexchanges=yes +8
Must-staplenot declared
Grades
Posture
C78
Speed
D62
Certificate
80
TLS profile
94
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://node.decimalchain.com/web3
Host
Chain ID
75
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_256_GCM_SHA384
Last seen
2026-11-16T20:20:10.014045062Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
1.07s
Latest block height
-

Using this RPC

tabs 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://node.decimalchain.com/web3' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:33:24.817Z
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.