https://rpc.swiftnodes.io/rpc/dymension

Dymensionevm

swiftnodes.io· rpc compare ↔

Posture score

Speed score

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

84d

Session resumed

yes

TLS handshake

164ms

Resumption

147ms

TTFB

1.04s

RPC block height

23,782,632

TLS handshake

VersionTLS 1.3

CipherTLS_AES_256_GCM_SHA384

KEX groupclassical

ALPNhttp/1.1

PQ classClassical only

Handshake164ms

Resumed?yes · 147ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrpc.swiftnodes.io

IssuerYE1

Key typeECDSA-P-256

Chain length4

SANsrpc.swiftnodes.io

Not before2026-10-02

Not after2026-12-31

Days to expiry84d

Chain SHA-2567b923f3813403a65…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

D68

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc.swiftnodes.io/rpc/dymension

Host

rpc.swiftnodes.io

Chain

Dymension

Chain ID

1100

evm

Platform type

chain

Sibling RPCs

view all on chain page →

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:04.392944102Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

387ms

Latest block height

Current fastest URL

https://dymension.api.onfinality.io/public

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.swiftnodes.io/rpc/dymension' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T11:29:32.920Z

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.