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

https://rpcmain.arabianchain.org

Dubxcoin networkevmarabianchain.org· rpcmaincompare ↔● fastest right now
Posture score
78
Speed score
83
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
3d
Session resumed
yes
TLS handshake
128ms
Resumption
109ms
TTFB
672ms
RPC block height
6,392,791
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake128ms
Resumed?yes · 109ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpcmain.arabianchain.org
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANsrpcmain.arabianchain.org
Not before2026-07-14
Not after2026-10-12
Days to expiry3d
Chain SHA-2560e479cde3e55ccbd…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
B83
Certificate
80
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://rpcmain.arabianchain.org
Host
Chain ID
3269
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-10-09T13:08:30.13754128Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
672ms
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://rpcmain.arabianchain.org' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:57:55.652Z
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.