Home / Network stats

Network

XDC Network Stats: Live Block Time, TPS and Masternodes

Over the last 24 hours the XDC Network made a block every 3.24 seconds on average and processed 9.65 transactions per second, counted by our server from every block. It has 108 active masternodes, and an epoch of 900 rounds lasts about 154 minutes.

Live XDC network status

Read from the newest blocks every minute: the last 30 blocks for block time and TPS.

Block height

109,525,800

Block time

10.62s

Transactions per second

3.3claimed 2,000

Base fee

12.5 Gwei

XDC RPC · updated 39s ago

XDC epoch, masternodes and burn

An epoch is 900 rounds of XDPoS 2.0. Masternodes are re-chosen and rewards are paid at each epoch switch.

Epoch

122,054

Round 18 of 900

Epoch progress

2.0%

Next epoch in about

110 min

Last 3 finished epochs, on average: 154.3 min, 819 blocks for 900 rounds

Active masternodes

108

267 standby · validator list

Burned since Cancun

62,979 XDC

XDC burn tracker

Latest block

109,525,800

Round 29,478,618

An 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 39s ago

XDC RPC (XDPoS) · updated 7 min ago

XDC RPC (base fee × gas used) · updated 38s ago

XDC block time history

Average seconds between blocks, counted from every block. Switch between 24 hours, 7 days and 30 days.

10.98s

Block time (average seconds per block)

XDC RPC, every block counted by our server · updated 34s 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

Transactions per second as measured on the chain, not the design claim.

3.3

Transactions per second (average over the hour)

XDC RPC, every block counted by our server · updated 34s 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

How much work the average block carried.

9.56M

Gas used per block (average over the hour)

XDC RPC, every block counted by our server · updated 34s 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

Blocks, transactions, block time, TPS and gas, with the slowest and busiest hour of each window.

XDC Network block time, transactions per second and gas used over 24 hours, 7 days and 30 days
MeasureLast 24 hoursLast 7 daysLast 30 days
Blocks made25,531213,8251,003,747
Transactions799,2277,967,30634,431,250
Average block time3.24 s2.81 s2.58 s
Slowest hour, block time14.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 second9.6513.313.3
Busiest hour, transactions per second17.6 (Nov 18, 17:00 UTC)24.2 (Nov 12, 17:00 UTC)24.4 (Oct 22, 03:00 UTC)
Average gas used per block1,356,138867,035868,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 34s 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 nameXDC Network
RPC URLhttps://erpc.xinfin.network
Chain ID50 (testnet: 51)
Currency symbolXDC
Block explorerhttps://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
Official list: XDC docs, mainnet RPC. Which of them answer right now, with response times and 30-day uptime, is on our XDC RPC status page. To look up a transaction, address or block, use the XDCScan explorer.

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

More XDC network data