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

https://node3-mainnet.decimalchain.com/web3

Decimal Smart Chain Mainnetevmdecimalchain.com· node3-mainnetcompare ↔
Posture score
83
Speed score
40
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
41d
Session resumed
yes
TLS handshake
275ms
Resumption
204ms
TTFB
1.56s
RPC block height
34,001,600
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake275ms
Resumed?yes · 204ms
OCSP stapledno
SCTs presentno
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 expiry41d
Chain SHA-256d5f0b962d7c3cdf3…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
F40
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://node3-mainnet.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_128_GCM_SHA256
Last seen
2026-10-07T23:57:36.608921136Z
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://node3-mainnet.decimalchain.com/web3' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:58:04.918Z
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.