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

https://rpc.flash.fuse.io

Fuse Testnetevmfuse.io· rpc.flashcompare ↔● fastest right now
Posture score
22
Speed score
-
TLS version
-
Cipher
-
KEX group
-
PQ class
PQ hybrid
ALPN
-
Cert expires in
-
Session resumed
-
TLS handshake
-
Resumption
-
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://rpc.flash.fuse.io": dial tcp: lookup rpc.flash.fuse.io on 127.0.0.53:53: server misbehaving
Endpoint identity
URL
https://rpc.flash.fuse.io
Host
Chain ID
12001
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
Unknown
Key exchange
-
Cipher
-
Last seen
-
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
-
Latest block height
-
Current fastest URL
https://rpc.flash.fuse.io
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://rpc.flash.fuse.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:32:21.121Z
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.