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

https://rpcapi.fantom.network

Fantom Operaevmfantom.network· rpcapicompare ↔
Posture score
83
Speed score
71
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
34d
Session resumed
yes
TLS handshake
172ms
Resumption
145ms
TTFB
967ms
RPC block height
123,591,632
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake172ms
Resumed?yes · 145ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpcapi.fantom.network
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsrpcapi.fantom.network
Not before2026-08-13
Not after2026-11-11
Days to expiry34d
Chain SHA-2562e8afd976c4647a8…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
C71
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://rpcapi.fantom.network
Host
Chain ID
250
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:45.152210518Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
455ms
Latest block height
-
Current fastest URL
https://fantom.drpc.org
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://rpcapi.fantom.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:33:17.556Z
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.