Main.netChain settings lookup

Chain profile

IoTeX chain ID 4689 and mainnet RPC URL

Source snapshot

Source evidence snapshot July 4, 2026. IoTeX documentation lists mainnet EVM chain ID 4689, IoTeX Foundation RPC endpoints, IOTX token details, and IoTeXScan.

Quick settings

IoTeX RPC status and chain ID answer

IoTeX mainnet uses chain ID 4689 / 0x1251, RPC URL https://babel-api.mainnet.iotex.io, explorer https://iotexscan.io, and IOTX as the gas token. Use the latest source check and linked docs to verify the fields before adding the network to a wallet, script, or app.

Chain ID
4689 / 0x1251
RPC URL
https://babel-api.mainnet.iotex.io
Explorer
https://iotexscan.io
Gas token
IOTX
Source docs
IoTeX docs
Latest check
Jul 20, 2026
Source snapshot
July 4, 2026
Config path
wallet_addEthereumChain JSON

Copy IoTeX configOpen source docsExplorer directoryGas token directory

Good fit when you need:
  • the IoTeX chain ID, RPC URL, explorer, and gas token in one place;
  • source documentation links beside the copied setup fields;
  • manual wallet config fields without connecting a wallet or choosing an RPC provider.
Before you paste these fields:
  • compare the chain ID against the source link on this page;
  • open the explorer once and confirm it matches the network you expect;
  • use the public RPC for setup checks, then choose monitored infrastructure for production traffic.
Chain ID4689 / 0x1251
RPC URLhttps://babel-api.mainnet.iotex.io
Explorerhttps://iotexscan.io
Gas tokenIOTX
VerificationVerified metadata
Source snapshotJuly 4, 2026
Evidence snapshot

Verification record

Automated source snapshots and recorded probe evidence are tracked separately. The source snapshot timestamp is not a manual review date. This is not a live uptime, latency, or production reliability monitor. If a recorded public RPC probe fails, verify the source links and current endpoint availability before changing production configuration.

Automated source snapshot
Verification status
Verified metadata
Source snapshot run
source-monitoring-2026-07-04
Source snapshot tool
source-monitoring-refresh
Source set
IoTeX docs
Latest recorded chain ID probe
eth_chainId matched expected 0x1251; observed 0x1251 on

MethodologyReport a correction

IoTeX wallet-add fields

Wallet directory sites often expose a connect button. Main.net keeps the same MetaMask and EIP-3085 setup fields as text so developers can compare them with official/source docs before calling wallet_addEthereumChain.

chainId
0x1251 (4689)
chainName
IoTeX
nativeCurrency
IOTX; name IOTX, symbol IOTX, decimals 18
rpcUrls
https://babel-api.mainnet.iotex.io
blockExplorerUrls
https://iotexscan.io
GlossaryChain IDHow wallet and RPC software identify a mainnet network.GlossaryRPC endpointWhat an RPC URL does and why public endpoints can be rate-limited.GlossaryMainnetThe production network context for these chain settings.Gas tokenIOTX gas tokenOther mainnet rows that use IOTX for gas.Network categoryEVM mainnetsCompare IoTeX with related evm mainnets by chain ID, RPC URL, explorer, and source links.Network categoryL1 mainnetsCompare IoTeX with related l1 mainnets by chain ID, RPC URL, explorer, and source links.GuideChain ID listChain IDs, RPC URLs, explorers, and source links across Main.net.

Monitoring evidence

These checks are review signals only. They are not uptime, latency, privacy, or production reliability claims. A source fetch failure or eth_chainId failure can mean a source page or public RPC endpoint was unavailable, changed, or rate-limited during a check. Re-open source links and test current RPC availability before relying on a public endpoint.

Snapshot generated
Source checks
2 sources checked
Source changes
0 changes since the previous source hash snapshot
Source fetch failures
0
eth_chainId probe
matched expected 0x1251
Per-source check timing
Included in the monitoring snapshot, not represented as a manual review or page freshness date

View monitoring snapshots orsource change history.

Network endpoints

Primary public RPC
https://babel-api.mainnet.iotex.io
Explorer
https://iotexscan.io
Official/source documentation
IoTeX docs
Chain type
EVM L1 mainnet
Chain ID hex
0x1251
Source snapshot provenance
source-monitoring-2026-07-04 via source-monitoring-refresh

IoTeX common questions

What is the IoTeX mainnet RPC URL?
IoTeX's listed primary public RPC URL is https://babel-api.mainnet.iotex.io.
What is IoTeX's chain ID?
IoTeX's listed chain ID is 4689.
What block explorer does IoTeX use?
IoTeX's listed block explorer is https://iotexscan.io.
What gas token does IoTeX use?
IoTeX's listed gas token is IOTX.

Copy-ready config

Neutral app configuration built from the verified fields above. Copy buttons only place text on your clipboard; they do not connect a wallet, request permissions, or rank RPC providers.

Chain ID decimal4689
Chain ID hex0x1251
RPC URLhttps://babel-api.mainnet.iotex.io
Explorer URLhttps://iotexscan.io
EIP-3085-shaped JSON

Rendered as text for manual review before use.

{
  "chainId": "0x1251",
  "chainName": "IoTeX",
  "nativeCurrency": {
    "name": "IOTX",
    "symbol": "IOTX",
    "decimals": 18
  },
  "rpcUrls": [
    "https://babel-api.mainnet.iotex.io"
  ],
  "blockExplorerUrls": [
    "https://iotexscan.io"
  ]
}

Developer snippets

Static examples generated from Main.net fields. These snippets are for manual configuration review and read-only RPC checks; they do not connect wallets, create signers, submit writes, or rank providers.

ts

viem chain definition

Read-only snippet generated from Main.net fields. Review official sources before production use.

import { defineChain } from 'viem'

export const iotexMainnet = defineChain({
  id: 4689,
  name: "IoTeX",
  nativeCurrency: {
    name: "IOTX",
    symbol: "IOTX",
    decimals: 18,
  },
  rpcUrls: {
    default: { http: ["https://babel-api.mainnet.iotex.io"] },
    public: { http: ["https://babel-api.mainnet.iotex.io"] },
  },
  blockExplorers: {
    default: {
      name: "iotexscan.io",
      url: "https://iotexscan.io",
    },
  },
})
ts

wagmi read-only config

Read-only transport example generated from Main.net fields. It does not include account adapters or transaction actions.

import { createConfig, http } from 'wagmi'
import { iotexMainnet } from './iotex'

export const config = createConfig({
  chains: [iotexMainnet],
  transports: {
    [iotexMainnet.id]: http("https://babel-api.mainnet.iotex.io"),
  },
})
ts

ethers read-only provider

Read-only JsonRpcProvider example generated from Main.net fields. It does not create a signer.

import { JsonRpcProvider } from 'ethers'

export const provider = new JsonRpcProvider("https://babel-api.mainnet.iotex.io", {
  chainId: 4689,
  name: "iotex",
})

const network = await provider.getNetwork()
console.log(network.chainId)
bash

curl eth_chainId check

Minimal JSON-RPC identity check. This verifies the endpoint-reported chain ID only, not uptime or production suitability.

curl -s -X POST \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
  https://babel-api.mainnet.iotex.io

# Expected chain ID: 4689 / 0x1251

Developer signals

External dashboards a developer may inspect before choosing where to deploy. Main.net links to these references but does not collect the metric values, normalize methodologies, rank chains, or recommend deployments.

explorerIoTeX explorerExplorer-hosted blocks, transactions, contracts, token transfers, and verification tools from the listed explorer.

Source links

IoTeX RPC endpointsIoTeX exchange integration

Safety note

IoTeX documentation separates full-node and archive endpoints. Use an archive or dedicated provider when historical state coverage is required.

Main.net is an independent reference site. It does not operate this chain, custody assets, execute transactions, or provide investment advice.

Report a correction

If this page has stale RPC, explorer, chain ID, or source information, open a public correction issue with a source link so it can be checked.

Report IoTeX dataSend page feedback