Chain profile

XDC Network chain ID 50 and mainnet RPC URL

Source snapshot

Source evidence snapshot July 4, 2026. XDC documentation lists XDC MainNet as EVM-compatible, chain/network ID 50, public RPC endpoints, XDCScan explorers, and XDC as the native token.

Quick settings

XDC Network RPC status and chain ID answer

XDC Network mainnet uses chain ID 50 / 0x32, RPC URL https://xdc.public-rpc.com, explorer https://xdcscan.com, and XDC 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
50 / 0x32
RPC URL
https://xdc.public-rpc.com
Explorer
https://xdcscan.com
Gas token
XDC
Source docs
XDC docs
Latest check
Jul 20, 2026
Source snapshot
July 4, 2026
Config path
wallet_addEthereumChain JSON

Copy XDC Network configOpen source docsExplorer directoryGas token directory

Good fit when you need:
  • the XDC Network 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 ID50 / 0x32
RPC URLhttps://xdc.public-rpc.com
Explorerhttps://xdcscan.com
Gas tokenXDC
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
XDC docs
Latest recorded chain ID probe
eth_chainId matched expected 0x32; observed 0x32 on

MethodologyReport a correction

XDC Network 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
0x32 (50)
chainName
XDC Network
nativeCurrency
XDC; name XDC, symbol XDC, decimals 18
rpcUrls
https://xdc.public-rpc.com
blockExplorerUrls
https://xdcscan.com

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 0x32
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://xdc.public-rpc.com
Explorer
https://xdcscan.com
Official/source documentation
XDC docs
Chain type
EVM L1 mainnet
Chain ID hex
0x32
Source snapshot provenance
source-monitoring-2026-07-04 via source-monitoring-refresh

XDC Network common questions

What is the XDC Network mainnet RPC URL?
XDC Network's listed primary public RPC URL is https://xdc.public-rpc.com.
What is XDC Network's chain ID?
XDC Network's listed chain ID is 50.
What block explorer does XDC Network use?
XDC Network's listed block explorer is https://xdcscan.com.
What gas token does XDC Network use?
XDC Network's listed gas token is XDC.

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 decimal50
Chain ID hex0x32
RPC URLhttps://xdc.public-rpc.com
Explorer URLhttps://xdcscan.com
EIP-3085-shaped JSON

Rendered as text for manual review before use.

{
  "chainId": "0x32",
  "chainName": "XDC Network",
  "nativeCurrency": {
    "name": "XDC",
    "symbol": "XDC",
    "decimals": 18
  },
  "rpcUrls": [
    "https://xdc.public-rpc.com"
  ],
  "blockExplorerUrls": [
    "https://xdcscan.com"
  ]
}

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 xdcNetworkMainnet = defineChain({
  id: 50,
  name: "XDC Network",
  nativeCurrency: {
    name: "XDC",
    symbol: "XDC",
    decimals: 18,
  },
  rpcUrls: {
    default: { http: ["https://xdc.public-rpc.com"] },
    public: { http: ["https://xdc.public-rpc.com"] },
  },
  blockExplorers: {
    default: {
      name: "xdcscan.com",
      url: "https://xdcscan.com",
    },
  },
})
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 { xdcNetworkMainnet } from './xdc-network'

export const config = createConfig({
  chains: [xdcNetworkMainnet],
  transports: {
    [xdcNetworkMainnet.id]: http("https://xdc.public-rpc.com"),
  },
})
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://xdc.public-rpc.com", {
  chainId: 50,
  name: "xdc-network",
})

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://xdc.public-rpc.com

# Expected chain ID: 50 / 0x32

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.

Safety note

XDC documentation lists multiple public RPC endpoints. Confirm endpoint policy and use dedicated infrastructure for production workloads.

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 XDC Network dataSend page feedback