RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://rpc.mainnet.oasys.games

Oasys Mainnetevmoasys.games· rpc.mainnetcompare ↔● fastest right now● PQ hybrid
Posture score
96
Speed score
87
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
40d
Session resumed
no
TLS handshake
77ms
Resumption
71ms
TTFB
717ms
RPC block height
14,918,116
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake77ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc.mainnet.oasys.games
IssuerYR2
Key typeRSA-4096
Chain length3
SANsrpc.mainnet.oasys.games
Not before2026-08-19
Not after2026-11-17
Days to expiry40d
Chain SHA-2564608f2f721b7a1c3…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
A+96
Speed
B87
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://rpc.mainnet.oasys.games
Host
Chain ID
248
VM
evm
Platform type
chain
Live probe (last 24 h)
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
TLS posture (post-quantum)full history →
Class
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_256_GCM_SHA384
Last seen
2026-10-07T23:57:44.838020452Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
717ms
Latest block height
-
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://rpc.mainnet.oasys.games' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:41:56.146Z
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.