https://evm-api.carbon.network

Carbon EVMevm

carbon.network· evm-api compare ↔

Posture score

Speed score

TLS version

0x0000

Cipher

0x0000

KEX group

PQ class

Unknown

ALPN

Cert expires in

Session resumed

TLS handshake

231ms

Resumption

TTFB

RPC block height

Prober warning: phase_b: Post "https://evm-api.carbon.network": tls: failed to verify certificate: x509: certificate is valid for api-binance-proxy.carbon.network, not evm-api.carbon.network

TLS handshake

Version0x0000

Cipher0x0000

KEX group-

ALPN-

PQ classUnknown

Handshake231ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subject-

Issuer-

Key type-

Chain length-

SANs-

Not before-

Not after-

Days to expiry-

Misconfigurations

TLS version older than 1.2 tls_too_old
ALPN not negotiated no_alpn
OCSP stapling not enabled no_ocsp_staple

Grades

Posture

F36

Speed

C70

Certificate

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://evm-api.carbon.network

Host

evm-api.carbon.network

Chain

Carbon EVM

Chain ID

9790

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

0x0000

Last seen

2026-10-10T07:33:55.245066454Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

https://evm-api.carbon.network/

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

Scan reportschema rpcscan-report · captured 2026-10-10T07:34:55.089Z

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.