Live XDC network status
Block height
109,525,762
Block time
17.03s
Transactions per second
2.1claimed 2,000
Base fee
12.5 Gwei
XDC RPC · updated 27s ago
XDC epoch, masternodes and burn
Epoch
122,053
Round 873 of 900Epoch progress
97.0%
Next epoch in about
3 min
Last 3 finished epochs, on average: 112.2 min, 847 blocks for 900 roundsLatest block
109,525,762
Round 29,478,573An epoch is 900 XDPoS rounds. Epoch, round and time left are read from the latest block; the time left uses the average length of the last finished epochs, so it is an estimate.
XDC RPC · updated 27s ago
XDC RPC (XDPoS) · updated 9 min ago
XDC RPC (base fee × gas used) · updated 27s ago
XDC block time history
10.98s
Block time (average seconds per block)
XDC RPC, every block counted by our server · updated 2 min ago
Each point is the hour (24 h, 7 d) or six hours (30 d) divided by the number of blocks in it, so it is the average time between blocks. An hour in which the chain made no blocks is left out. Hours are in UTC.
XDC TPS history
3.3
Transactions per second (average over the hour)
XDC RPC, every block counted by our server · updated 2 min ago
Transactions in the period divided by its seconds. It counts every transaction in every block, including simple transfers and contract calls, and is an average: single seconds can be higher. XDC's own documents claim up to 2,000 TPS; that is a design claim, not what is measured here. Hours are in UTC.
XDC gas used per block
9.56M
Gas used per block (average over the hour)
XDC RPC, every block counted by our server · updated 2 min ago
Gas used by the blocks in the period divided by their number. Gas is the unit that prices work on the chain; a plain transfer uses 21,000. Since Nov 15, 11:00 UTC every block is counted; for earlier hours the figure comes from 12 blocks sampled across the hour. Hours are in UTC.
XDC network stats: 24 hours, 7 days and 30 days
| Measure | Last 24 hours | Last 7 days | Last 30 days |
|---|---|---|---|
| Blocks made | 25,531 | 213,825 | 1,003,747 |
| Transactions | 799,227 | 7,967,306 | 34,431,250 |
| Average block time | 3.24 s | 2.81 s | 2.58 s |
| Slowest hour, block time | 14.23 s (Nov 19, 00:00 UTC) | 20.11 s (Nov 16, 19:00 UTC) | 20.11 s (Nov 16, 19:00 UTC) |
| Average transactions per second | 9.65 | 13.3 | 13.3 |
| Busiest hour, transactions per second | 17.6 (Nov 18, 17:00 UTC) | 24.2 (Nov 12, 17:00 UTC) | 24.4 (Oct 22, 03:00 UTC) |
| Average gas used per block | 1,356,138 | 867,035 | 868,480 |
Counted from every block by our server up to Nov 19, 02:00 UTC; the hour in progress is added once it has ended. A window holds only the complete hours counted so far.
XDC RPC, every block counted by our server · updated 2 min ago
XDC block time, TPS and base fee explained
Block height: the latest XDC block
The number of the latest block. It rises by one with every new block, every few seconds.
Block time: how fast XDC makes blocks
The average time between the last 30 blocks, measured from the blocks themselves.
Transactions per second: current XDC throughput
What the network is actually processing now, not its maximum. XDC's documentation claims about 2,000 TPS (XDC docs); real usage is much lower, which is normal for most blockchains.
Base fee: the minimum XDC transaction fee
The minimum fee per unit of gas. Since the Cancun upgrade in January 2026 it is burned, which is what our burn tracker counts.
Is XDC still active? These live figures are the first thing to check: a chain that has stopped would show no new blocks. Is XDC dead? How to check the on-chain activity goes through the other signals, from transactions to developer work and exchange listings.
What network is XDC on?
XDC is the native coin of its own blockchain, the XDC Network. It is not a token on Ethereum or Solana, although the network runs the same smart-contract engine (the EVM) as Ethereum, so Ethereum wallets and tools work with it once the network is added (XDC MiCA white paper).
Mainnet and testnet
XDC mainnet uses chain ID 50. The Apothem testnet, for developers, uses chain ID 51. Both IDs are what wallets use to tell networks apart (XDC docs).
Before mainnet: the XDCE token
Before the mainnet launched on 1 June 2019, XDC existed as XDCE, an ERC-20 token on Ethereum, which was swapped one for one for native XDC (MiCA white paper). Tokens called XDC on other chains today are not the native coin.
Who runs it
No single company runs the network: blocks are produced by independent masternode operators who each stake at least 10 million XDC (xinfin.org). XinFin Fintech Pte. Ltd. in Singapore issued XDC in 2017, and the XDC Foundation (Cayman Islands, 2021) supports the ecosystem (MiCA white paper).
How XDC reaches consensus: XDPoS 2.0
XDC uses XDPoS 2.0, a delegated proof-of-stake design that went live on 30 September 2024 (xdc.org, XDC 2.0 overview).
Masternodes produce and confirm blocks
xinfin.org lists 108 core validator places, each needing at least 10 million XDC, with protector and standby nodes behind them for redundancy (xinfin.org). The live list is on the validators page.
Final within a few blocks
A block is final once three more blocks confirm it, so a transaction cannot be reversed a few block times after it is included (xdc.org).
Rewards every epoch
Rewards are paid every epoch of 900 rounds (XDPoSChain, epoch switch rule); its live length is on the masternode calculator. What each tier earns is on the masternodes page.
Is XDC fast? XDC compared with other networks
- XDC: about 2 seconds per block by design, final after three more blocks (xdc.org). The live block time is shown above.
- Ethereum: time is divided into 12-second slots (ethereum.org).
- XRP Ledger: new ledger versions usually close about every 3 to 5 seconds (xrpl.org).
Block time is only one measure. Real throughput depends on how full blocks are and on how many transactions people send. For a full comparison see XDC vs XRP.
What an XDC transaction costs
Every transaction pays for the gas it uses. The fee is the gas used multiplied by the base fee shown above, plus an optional tip for the validator. A plain XDC transfer uses 21,000 gas, the same as on Ethereum, so its fee is 21,000 times the live base fee; smart-contract calls use more gas.
Since the Cancun upgrade went live at block 98,800,200 in January 2026, the base fee part of every fee is burned instead of paid out (Cancun release notes). How much has been burned so far is on the burn tracker.
XDC network milestones
- 2017: XinFin Fintech issues XDC (MiCA white paper).
- 1 June 2019: mainnet launch; XDCE swapped for native XDC (MiCA white paper).
- 30 September 2024: XDPoS 2.0 consensus goes live (xdc.org).
- January 2026: Cancun upgrade (v2.6.8) at block 98,800,200 adds EIP-1559 base-fee burning (release notes).
XDC chain ID: add XDC to MetaMask
Add XDC mainnet (chain ID 50) or the Apothem testnet (chain ID 51) to MetaMask in one click:
Works with MetaMask and other browser wallets.
| Network name | XDC Network |
|---|---|
| RPC URL | https://erpc.xinfin.network |
| Chain ID | 50 (testnet: 51) |
| Currency symbol | XDC |
| Block explorer | https://xdcscan.com |
XDC RPC URLs and block explorer
These public endpoints answer standard Ethereum JSON-RPC calls for XDC mainnet. We read our network data from them.
- https://erpc.xinfin.network
- https://rpc.xinfin.network
- https://rpc1.xinfin.network
- https://erpc.xdcrpc.com
How much XDC do you need to run a node?
Anyone can run a full node to read the chain without staking (xinfin.org). To produce blocks as a masternode you need at least 10 million XDC and a dedicated or cloud server that stays online all the time (xinfin.org). Most holders stake through a provider instead; see XDC staking. The setup for both kinds of node, step by step, is in how to run an XDC node or masternode.
How we measure XDC block time, TPS and gas
The charts and the table count every block of the XDC Network. Our server reads each block's header from public XDC RPC nodes (the same read that feeds our burn tracker) and adds up blocks, transactions and gas for every hour. Nothing is estimated from a sample, except as noted for gas below.
Block time
For each hour we divide 3,600 seconds by the number of blocks made in it, so the figure is the average time between blocks. The chain is built for a block every 2 seconds: the mainnet configuration sets a 2-second period (XDPoSChain, genesis/mainnet.json; params/config_networks.go). In XDPoS 2.0 a round in which the masternodes time out makes no block, so the measured average can sit above the design value (XDPoSChain, epoch switch rule). An hour with no blocks at all has no value and is left out of the chart.
Transactions per second
Transactions in the period divided by its seconds. It counts every transaction in every block, simple transfers and contract calls alike. It is an average over the hour (24 hours and 7 days) or six hours (30 days), so a single busy second can be higher; the table shows the busiest hour. XDC's own material claims up to 2,000 TPS (XDC docs); that is a design claim, and this page shows what the chain actually carried.
Gas used per block
Gas is the unit that prices work on the chain: a plain XDC transfer uses 21,000. We add the gas used by the blocks in the period and divide by their number. Since our server started counting gas, every block is included; for the 30 days before that, each hour is estimated from 12 blocks spread evenly across it, and the note under the gas chart says from when every block is counted. The block gas limit is set by each block producer's node, not by a vote or a fixed rule, within a limit on how far it may change from one block to the next (XDPoSChain, miner/worker.go), so gas per block alone does not say how full blocks are.
Epochs and rounds
XDPoS 2.0 counts time in rounds, and an epoch is 900 rounds (XDPoSChain, epoch switch rule). Our server reads the round of the latest block from the node's XDPoS interface (XDPoSChain, XDPoS API), counts the epoch the way the node does (the epoch at the XDPoS 2.0 switch, 89,300 in genesis/mainnet.json, plus the round divided by 900) and takes the remainder as the position. The time left uses the average length of the last finished epochs (up to three), found from the epoch-switch blocks, so it is an estimate: timeouts can stretch an epoch. The number of masternodes is the active set the node reports for the latest block.
What these figures do not say
They describe how much the network is used and how steadily it makes blocks. They do not rate the network's security, say anything about the price, or predict anything. A quiet hour can mean few users; it can also mean a node problem on our side, so the page shows when the figures were last counted.
Where the data can be wrong
Our server asks several public XDC RPC nodes in turn. If all of them fail for a while, the newest hours appear late and the line under each chart shows the last update time; hours already counted do not change. The live panel at the top reads only the last 30 blocks, so it moves much more than the hourly charts. There is no node map on this page: XinFin's network statistics service is not among the hosts our server may call.
For what the numbers mean in everyday terms, see the sections above; for the fee side of gas, the XDC burn tracker shows how much of every fee is burned, and the validator list shows who produces the blocks.
XDC network FAQ
Its own layer-1 blockchain, the XDC Network (chain ID 50). XDC is the network's native coin, used to pay fees and to stake.
No. XDC has its own blockchain. It runs the same smart-contract engine as Ethereum, so Ethereum wallets such as MetaMask work once you add the XDC network.
No. The native XDC coin only exists on the XDC Network. A token called XDC on another chain is not the native coin.
A new block every few seconds (about two seconds by design), final after three more blocks. The live block time is shown at the top of this page.
XDC is designed for a block about every two seconds; XRP Ledger versions usually close every 3 to 5 seconds, according to xrpl.org. Both are fast enough for payments; see XDC vs XRP.
50 for mainnet and 51 for the Apothem testnet.
At least 10 million XDC to run a masternode that produces blocks. A full node that only reads the chain needs no stake.
The network is built for a block every 2 seconds. The average we measure from every block over the last 24 hours, 7 days and 30 days is in the table above and in the block time chart; it can differ from 2 seconds because a round that times out makes no block.
The live figure at the top averages the last 30 blocks, and the history chart shows transactions per second averaged over each hour, counted from every block. XDC's own material claims up to 2,000 TPS; that is a design claim, not a measurement.
Up to 108 active masternodes produce blocks in each epoch (source). The live active and standby counts are in the epoch panel and, address by address, on the validators page.
A stretch of 900 rounds of XDPoS 2.0. At each epoch switch the active masternodes are chosen again and rewards are paid. The panel above shows the current epoch, how far it is and about how long is left.
Public XDC RPC nodes. Our server counts every block into hourly totals, so the charts are our own measurements and not a copy of another site. Each chart shows when it was last updated.
Nobody owns the network itself; independent masternode operators produce the blocks. XinFin Fintech issued XDC in 2017, and the XDC Foundation supports the ecosystem.