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

https://pulsechain-testnet-rpc.publicnode.com

PulseChain Testnet v4evmpublicnode.com· pulsechain-testnet-rpccompare ↔● fastest right now● PQ hybrid
Posture score
96
Speed score
100
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
86d
Session resumed
yes
TLS handshake
20ms
Resumption
11ms
TTFB
99ms
RPC block height
25,586,454
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake20ms
Resumed?yes · 11ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectpublicnode.com
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANspublicnode.com, *.publicnode.com
Not before2026-10-05
Not after2027-01-03
Days to expiry86d
Chain SHA-256be3d917dbd77fa0b…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
A+96
Speed
A+100
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://pulsechain-testnet-rpc.publicnode.com
Host
Chain ID
943
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-08T08:13:00.913926242Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
99ms
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://pulsechain-testnet-rpc.publicnode.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:36:52.024Z
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.