https://mainnet.datagram.network/rpc

Datagramevm

datagram.network· mainnet 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

150d

Session resumed

yes

TLS handshake

254ms

Resumption

266ms

TTFB

1.34s

RPC block height

2,737,742

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPN-

PQ classClassical only

Handshake254ms

Resumed?yes · 266ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectmainnet.datagram.network

IssuerAmazon RSA 2048 M04

Key typeRSA-2048

Chain length3

SANsmainnet.datagram.network

Not before2026-08-21

Not after2027-03-06

Days to expiry150d

Chain SHA-2567b06e970ee0fe7af…

Misconfigurations

ALPN not negotiated no_alpn
OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B81

Speed

D61

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://mainnet.datagram.network/rpc

Host

mainnet.datagram.network

Chain

Datagram

Chain ID

968

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

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:57:36.349Z

SHA-256 of canonical content

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.