https://rollapp.jrpc.cumulo.com.es

Dymensionevm

com.es· rollapp.jrpc.cumulo compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

85d

Session resumed

yes

TLS handshake

91ms

Resumption

140ms

TTFB

683ms

RPC block height

23,782,632

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake91ms

Resumed?yes · 140ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrollapp.jrpc.cumulo.com.es

IssuerYE1

Key typeECDSA-P-256

Chain length4

SANsrollapp.jrpc.cumulo.com.es

Not before2026-10-03

Not after2027-01-01

Days to expiry85d

Chain SHA-256a6a6fe9fcab334ee…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

A90

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rollapp.jrpc.cumulo.com.es

Host

rollapp.jrpc.cumulo.com.es

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_128_GCM_SHA256

Last seen

2026-10-07T23:58:04.580640907Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

239ms

Latest block height

Current fastest URL

https://dymension.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://rollapp.jrpc.cumulo.com.es' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T07:38:10.222Z

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.