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

https://evm-rpc.story.mainnet.dteam.tech

Data Networkevmdteam.tech· evm-rpc.story.mainnetcompare ↔
Posture score
83
Speed score
95
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
73d
Session resumed
no
TLS handshake
78ms
Resumption
72ms
TTFB
377ms
RPC block height
20,818,218
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake78ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectapi.story.mainnet.dteam.tech
IssuerYR1
Key typeRSA-2048
Chain length3
SANsapi.story.mainnet.dteam.tech, evm-rpc.story.mainnet.dteam.tech, evm-rpc.wss.story.mainnet.dteam.tech +1
Not before2026-09-21
Not after2026-12-20
Days to expiry73d
Chain SHA-25626f67974db7f6540…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
A+95
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://evm-rpc.story.mainnet.dteam.tech
Host
Chain ID
1514
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-07T23:58:10.88163574Z
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://evm-rpc.story.mainnet.dteam.tech' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:48:25.081Z
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.