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, 167 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/oktc-rpc. 2 public endpoints, no key: exchainrpc.okex.org, oktc.drpc.org. 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: 2 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: 2 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: 2 free public OKTC RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | OKX Chain Official | 167 ms | 182 ms | 500 ms | 100.00% |
| 2 | dRPC | 344 ms | 450 ms | 647 ms | 90.20% |
Public OKTC RPC endpoints measured
The 2 no-key endpoints answering our probes today, with their current 24h median. 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.org167 ms100.0%
dRPChttps://oktc.drpc.org344 ms90.2%
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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- 1RPC
https://1rpc.io/oktc2.4 % success over 24 h
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