http://dappnode3.ont.io:20339

Ontology Mainnetevm

ont.io· dappnode3 compare ↔

Posture score

Speed score

TLS version

Cipher

KEX group

PQ class

Unknown

ALPN

Cert expires in

Session resumed

TLS handshake

Resumption

TTFB

824ms

RPC block height

20,901,808

Endpoint identity

URL

http://dappnode3.ont.io:20339

Host

dappnode3.ont.io

Chain

Ontology Mainnet

Chain ID

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

Unknown

Key exchange

Cipher

Last seen

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

758ms

Latest block height

Current fastest URL

http://dappnode4.ont.io:20339

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

Scan reportschema rpcscan-report · captured 2026-10-10T06:45:54.233Z

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.