https://api.uniblock.dev/uni/v1/json-rpc?chainId=151

Redbelly Network Mainnetevm

uniblock.dev· api 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

79d

Session resumed

yes

TLS handshake

314ms

Resumption

196ms

TTFB

1.98s

RPC block height

3,220,809

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake314ms

Resumed?yes · 196ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectapi.uniblock.dev

IssuerWR3

Key typeRSA-2048

Chain length3

SANsapi.uniblock.dev

Not before2026-09-29

Not after2026-12-28

Days to expiry79d

Chain SHA-2561636688bfafdffd6…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

F39

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://api.uniblock.dev/uni/v1/json-rpc?chainId=151

Host

api.uniblock.dev

Chain

Redbelly Network Mainnet

Chain ID

151

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-10T06:37:43.15540135Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

828ms

Latest block height

Current fastest URL

https://rpc.ankr.com/redbelly_mainnet

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://api.uniblock.dev/uni/v1/json-rpc?chainId=151' \
  -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.156Z

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.