https://mycrypto.rsk.co

Rootstock Mainnetevm

rsk.co· mycrypto 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

107d

Session resumed

TLS handshake

276ms

Resumption

197ms

TTFB

1.52s

RPC block height

9,305,947

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake276ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subjectpub-node.rsk.co

IssuerAmazon ECDSA 384 M04

Key typeECDSA-P-384

Chain length3

SANspub-node.rsk.co, mycrypto.rsk.co, metamask.mainnet.rsk.co +1

Not before2026-07-09

Not after2027-01-22

Days to expiry107d

Chain SHA-25647b09f0250261664…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

F48

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://mycrypto.rsk.co

Host

mycrypto.rsk.co

Chain

Rootstock 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

Classical only

Key exchange

Cipher

TLS_AES_128_GCM_SHA256

Last seen

2026-10-07T23:57:33.582539232Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:48:00.548Z

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.