https://lens-mainnet.g.alchemy.com/public

Lensevm

alchemy.com· lens-mainnet.g 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

40d

Session resumed

TLS handshake

37ms

Resumption

51ms

TTFB

471ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake37ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subject*.g.alchemy.com

IssuerYR2

Key typeRSA-2048

Chain length3

SANs*.g.alchemy.com, mpp.alchemy.com, x402.alchemy.com

Not before2026-08-19

Not after2026-11-17

Days to expiry40d

Chain SHA-2562498b3e36481c723…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

D66

Speed

A93

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://lens-mainnet.g.alchemy.com/public

Host

lens-mainnet.g.alchemy.com

Chain

Lens

Chain ID

232

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:44.474591792Z

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

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

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.