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 has the lowest median latency of the 2 free public OKTC RPC endpoints measured above the 50 % success floor (3 listed), 162 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 162 ms; the chain-official endpoint measures 162 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.
Results: 3 free public OKTC RPC endpoints measured, 2 ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | OKX Chain Official | 162 ms | 172 ms | 460 ms | 99.98% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | dRPC | 347 ms | 447 ms | 669 ms | 92.60% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Measured, not ranked: sample below the ranking floor | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| not ranked | 1RPC | 391 ms | 5.21 s | 7.24 s | 17.80% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Public OKTC RPC endpoints measured
The 3 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is 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 Officialhttps://exchainrpc.okex.org162 ms100.0%
dRPChttps://oktc.drpc.org347 ms92.6%
1RPChttps://1rpc.io/oktc391 ms17.8% ▾
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