https://rpc3.mainnet.1money.network

1Money Network Mainnetevm

1money.network· rpc3.mainnet compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

PQ class

Unknown

ALPN

Cert expires in

154d

Session resumed

TLS handshake

143ms

Resumption

TTFB

501ms

RPC block height

1,496,369

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX group-

ALPNh2

PQ classUnknown

Handshake143ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subjectmainnet.1money.network

IssuerAmazon RSA 2048 M01

Key typeRSA-2048

Chain length3

SANsmainnet.1money.network, *.mainnet.1money.network

Not before2026-08-28

Not after2027-03-13

Days to expiry154d

Chain SHA-25643f2408c7c070d4c…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C73

Speed

B81

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc3.mainnet.1money.network

Host

rpc3.mainnet.1money.network

Chain

1Money Network Mainnet

Chain ID

21210

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

TLS_AES_128_GCM_SHA256

Last seen

2026-10-10T05:53:52.102801966Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:58:33.713Z

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.