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

wss://rpc.btcw.tech/ws

Bitcoin Swapevmbtcw.tech· rpccompare ↔
Posture score
83
Speed score
17
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
67d
Session resumed
yes
TLS handshake
-
Resumption
4.44s
TTFB
-
RPC block height
396,664
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake-
Resumed?yes · 4.44s
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.btcw.tech
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsapp.btcw.tech, btcw.tech, explorer.btcw.tech +1
Not before2026-09-23
Not after2026-12-22
Days to expiry67d
Chain SHA-25646ea3ad95f4bf614…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B83
Speed
F17
Certificate
100
TLS profile
92
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
wss://rpc.btcw.tech/ws
Host
Chain ID
482120
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-15T21:12:48.461106004Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
2.61s
Latest block height
-
Current fastest URL
https://rpc.btcw.tech
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 'wss://rpc.btcw.tech/ws' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-15T21:56:01.895Z
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.