RPCsUpdated

OKTC RPC endpoints: free public URLs by latency

HTTP round-trip latency for eth_getBlockByNumber against every available public OKTC node, audited every 60 seconds from 3 regions.

TL;DR. As of , OKX Chain Official is the only one of the 3 free public OKTC RPC endpoints measured above the 50 % success floor, at 167 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/oktc-rpc. 3 public endpoints, no key: exchainrpc.okex.org, oktc.drpc.org, 1rpc.io. Full URLs with their 24h median are listed below.

Companion page

Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →

OKTC (OKX Token Chain, formerly OKChain) is an EVM-compatible Layer 1 blockchain (chain ID 66) developed by OKX, targeting high throughput and low fees for DeFi applications. It exposes a standard Ethereum JSON-RPC interface. Public EVM endpoints are available without an API key from OKX Chain Official, 1RPC and dRPC. Every provider was live-verified with consecutive eth_getBlockByNumber probes at launch.

Methodology

OKTC: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. OKX Chain Official leads at 167 ms; the chain-official endpoint measures 167 ms. We measure the round-trip latency of a single eth_getBlockByNumber ("latest", false) call against every available public OKTC node that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a standard EVM staleness gap. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the OKTC-scoped answer with per-region breakdowns as a first-class dimension.

  • Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus avg(quantile_over_time(...)); per-region breakdowns are first-class on this page via the region tabs.
  • Payload: {"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}. Plain HTTP POST. Standard Ethereum JSON-RPC 2.0.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the OKTC-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain=oktc. Provider coverage today: 3 endpoints.

Results: 3 free public OKTC RPC endpoints measured, 1 ranked by p50 latency (24h, 3 regions)

OKTC RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1OKX Chain OfficialOKX Chain official public RPC (exchainrpc.okex.org), keyless167 ms176 ms387 ms51.93% (n=4318)
Measured, not ranked: sample below the ranking floor
not rankeddRPCdRPC decentralised multi-chain RPC, public OKTC endpoint, no key required335 ms425 ms596 ms42.98% (n=4315)
not ranked1RPC1RPC privacy-preserving public OKTC endpoint, keyless839 ms4.87 s7.43 s6.40% (n=4313)

Public OKTC RPC endpoints measured

The 3 no-key endpoints answering our probes today, with their current 24h median; 2 of them sit below the 50 % success floor and are listed last. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.

  • OKX Chain Official logoOKX Chain Officialhttps://exchainrpc.okex.org167 ms51.9%
  • dRPC logodRPChttps://oktc.drpc.org335 ms43.0% ▾
  • 1RPC logo1RPChttps://1rpc.io/oktc839 ms6.4% ▾

Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.

Frequently asked

Which OKTC RPC endpoints work without an API key?

3 endpoints are probed on this chain: OKX Chain Official (exchainrpc.okex.org), 1RPC (1rpc.io/oktc) and dRPC (oktc.drpc.org). Every listed endpoint was live-verified with an eth_getBlockByNumber call returning a parsable block number before inclusion.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities