Active XDC masternodes
Active masternodes
108
Standby nodes
267
Under penalty
5
Round
29,478,539
| Explorer | |||
|---|---|---|---|
| 1 | xdce79e…ee78d | Active | XDCScan ↗ |
| 2 | xdcbbd2…35cfe | Active | XDCScan ↗ |
| 3 | xdc2f68…a1bd4 | Active | XDCScan ↗ |
| 4 | xdc49d3…6c713 | Active | XDCScan ↗ |
| 5 | xdcb9a3…17708 | Active | XDCScan ↗ |
| 6 | xdc2139…ef80e | Active | XDCScan ↗ |
| 7 | xdc76df…55a05 | Active | XDCScan ↗ |
| 8 | xdc070e…0bfe6 | Active | XDCScan ↗ |
| 9 | xdc5454…8bedc | Active | XDCScan ↗ |
| 10 | xdc83e1…7ee23 | Active | XDCScan ↗ |
| 11 | xdc9200…5b99f | Active | XDCScan ↗ |
| 12 | xdc0002…c9d1f | Active | XDCScan ↗ |
| 13 | xdc2edd…19f06 | Active | XDCScan ↗ |
| 14 | xdc7c0f…fc8c9 | Active | XDCScan ↗ |
| 15 | xdcbb08…d6b00 | Active | XDCScan ↗ |
| 16 | xdc75ea…c5221 | Active | XDCScan ↗ |
| 17 | xdcf480…0442d | Active | XDCScan ↗ |
| 18 | xdc9bbf…51864 | Active | XDCScan ↗ |
| 19 | xdc361f…c5858 | Active | XDCScan ↗ |
| 20 | xdc3495…3d3f3 | Active | XDCScan ↗ |
| 21 | xdc226d…e375b | Active | XDCScan ↗ |
| 22 | xdc249f…41a47 | Active | XDCScan ↗ |
| 23 | xdce8bc…91e32 | Active | XDCScan ↗ |
| 24 | xdc7fca…44a9c | Active | XDCScan ↗ |
| 25 | xdc44d2…d9505 | Active | XDCScan ↗ |
| 26 | xdc2e32…ce18f | Active | XDCScan ↗ |
| 27 | xdc74f2…2b61f | Active | XDCScan ↗ |
| 28 | xdcb570…ac9fa | Active | XDCScan ↗ |
| 29 | xdc2a45…6a992 | Active | XDCScan ↗ |
| 30 | xdcde14…f328c | Active | XDCScan ↗ |
| 31 | xdc370b…40481 | Active | XDCScan ↗ |
| 32 | xdc4288…93ad4 | Active | XDCScan ↗ |
| 33 | xdcfab2…ca299 | Active | XDCScan ↗ |
| 34 | xdcef7c…47447 | Active | XDCScan ↗ |
| 35 | xdca454…c28ae | Active | XDCScan ↗ |
| 36 | xdc695c…d07dd | Active | XDCScan ↗ |
| 37 | xdcc7bf…e9b4b | Active | XDCScan ↗ |
| 38 | xdc3dd2…99480 | Active | XDCScan ↗ |
| 39 | xdc6f35…71eec | Active | XDCScan ↗ |
| 40 | xdceb0f…c6cb7 | Active | XDCScan ↗ |
| 41 | xdcaf3d…3024f | Active | XDCScan ↗ |
| 42 | xdc7b07…ddeb4 | Active | XDCScan ↗ |
| 43 | xdc8eee…74ff2 | Active | XDCScan ↗ |
| 44 | xdce02c…0882e | Active | XDCScan ↗ |
| 45 | xdca6de…9df9c | Active | XDCScan ↗ |
| 46 | xdc6e5b…2753d | Active | XDCScan ↗ |
| 47 | xdca9c2…8ce87 | Active | XDCScan ↗ |
| 48 | xdc618e…12d6a | Active | XDCScan ↗ |
| 49 | xdc58f2…60367 | Active | XDCScan ↗ |
| 50 | xdc9e05…b7739 | Active | XDCScan ↗ |
| 51 | xdcb594…1319a | Active | XDCScan ↗ |
| 52 | xdc4e11…d95d9 | Active | XDCScan ↗ |
| 53 | xdc241f…27c05 | Active | XDCScan ↗ |
| 54 | xdc03d9…6c9ff | Active | XDCScan ↗ |
| 55 | xdc1a7c…f02d4 | Active | XDCScan ↗ |
| 56 | xdca465…dbdb2 | Active | XDCScan ↗ |
| 57 | xdca70b…8eace | Active | XDCScan ↗ |
| 58 | xdca72c…7a962 | Active | XDCScan ↗ |
| 59 | xdc6219…c8418 | Active | XDCScan ↗ |
| 60 | xdc6344…5ab7f | Active | XDCScan ↗ |
| 61 | xdca4f1…c1cc1 | Active | XDCScan ↗ |
| 62 | xdc4584…a0fb8 | Active | XDCScan ↗ |
| 63 | xdc8073…ef7da | Active | XDCScan ↗ |
| 64 | xdcd7a6…98f4a | Active | XDCScan ↗ |
| 65 | xdc5c71…78576 | Active | XDCScan ↗ |
| 66 | xdc2a4b…dde17 | Active | XDCScan ↗ |
| 67 | xdc745a…dfcd5 | Active | XDCScan ↗ |
| 68 | xdca4ae…ff83d | Active | XDCScan ↗ |
| 69 | xdc0fb4…b8322 | Active | XDCScan ↗ |
| 70 | xdc8615…79f1c | Active | XDCScan ↗ |
| 71 | xdc1ffc…96f3e | Active | XDCScan ↗ |
| 72 | xdc0302…8cd57 | Active | XDCScan ↗ |
| 73 | xdc149e…fb0fe | Active | XDCScan ↗ |
| 74 | xdc5ccd…6b89e | Active | XDCScan ↗ |
| 75 | xdc047f…9f470 | Active | XDCScan ↗ |
| 76 | xdc74d3…30c4b | Active | XDCScan ↗ |
| 77 | xdcb169…fb40d | Active | XDCScan ↗ |
| 78 | xdc2a59…9feb2 | Active | XDCScan ↗ |
| 79 | xdc449b…2bc21 | Active | XDCScan ↗ |
| 80 | xdccc82…c3b6c | Active | XDCScan ↗ |
| 81 | xdcd64c…a318e | Active | XDCScan ↗ |
| 82 | xdc7850…c01d5 | Active | XDCScan ↗ |
| 83 | xdc3b8a…38766 | Active | XDCScan ↗ |
| 84 | xdc079d…81fb4 | Active | XDCScan ↗ |
| 85 | xdca43a…1e617 | Active | XDCScan ↗ |
| 86 | xdc0407…09487 | Active | XDCScan ↗ |
| 87 | xdcebf8…f83d3 | Active | XDCScan ↗ |
| 88 | xdca828…c4b5b | Active | XDCScan ↗ |
| 89 | xdc90c8…c2f04 | Active | XDCScan ↗ |
| 90 | xdc0f0c…afeed | Active | XDCScan ↗ |
| 91 | xdc64e2…b4443 | Active | XDCScan ↗ |
| 92 | xdc391f…8658c | Active | XDCScan ↗ |
| 93 | xdcf5e2…49e09 | Active | XDCScan ↗ |
| 94 | xdc825c…fdc93 | Active | XDCScan ↗ |
| 95 | xdce25c…28a54 | Active | XDCScan ↗ |
| 96 | xdc4b70…7b746 | Active | XDCScan ↗ |
| 97 | xdce2bc…75db7 | Active | XDCScan ↗ |
| 98 | xdc609c…9f819 | Active | XDCScan ↗ |
| 99 | xdce865…94b21 | Active | XDCScan ↗ |
| 100 | xdc25c6…2eaff | Active | XDCScan ↗ |
| 101 | xdce494…4a8a7 | Active | XDCScan ↗ |
| 102 | xdcccab…08a2c | Active | XDCScan ↗ |
| 103 | xdcb38a…60b6a | Active | XDCScan ↗ |
| 104 | xdce8e8…8729d | Active | XDCScan ↗ |
| 105 | xdc2d74…9e821 | Active | XDCScan ↗ |
| 106 | xdc92d3…4d2c8 | Active | XDCScan ↗ |
| 107 | xdc9043…2763f | Active | XDCScan ↗ |
| 108 | xdcc67c…196ab | Active | XDCScan ↗ |
XDC RPC (XDPoS) · updated 9 min ago
How to read the validator table
The table comes from an XDC RPC node, using the XDPoS_getMasternodesByNumber method: the same list the network uses to decide who signs the next blocks. The four figures above it and the list of addresses mean the following.
Active masternodes
The validators that produce and sign blocks in the current epoch. The active set holds at most 108 masternodes (xinfin.org, XDC docs, slashing). Every address in the list is an active validator.
Standby nodes
Candidates that have staked at least 10 million XDC but are not in the active set. The XDC docs describe standby nodes as identical in form and function to validators, except that they do not create blocks; they wait to fill the place of validators that drop out (XDC docs, masternode).
Under penalty
Candidates the protocol has excluded for the time being, usually for not signing blocks. They are counted here but are neither in the active list nor on standby until the penalty ends.
Round
The consensus round counter of XDPoS 2.0. In each round one masternode proposes a block. If no block arrives in time, the masternodes sign a timeout and move to the next round, so the counter runs a little ahead of the number of blocks produced since XDPoS 2.0 started. An epoch is 900 rounds; how far the current one has run, and the block time and TPS history, are on the XDC network stats page.
Addresses and the explorer link
Each row shows the masternode's address in xdc format. The same address with 0x in place of xdc is the form wallets and tools for Ethereum expect; our address converter switches between them. The XDCScan link opens the address on a block explorer. Operator names are not published on-chain, so we only show what the chain reports.
Want to run one of these nodes yourself? Our guide on how to run an XDC node or masternode covers the server, the setup steps and the 10 million XDC stake, and a full node that needs no stake at all.
How XDC chooses its validators
XDC runs XDPoS 2.0, a delegated proof-of-stake consensus built on the HotStuff protocol. The network switched to it on 30 September 2024 at block 80,370,000 (xdc.org). Who becomes a validator is decided by the validator smart contract at address 0x…0088 and by the node software (XDCValidator.sol). The minimums below were read from that contract on 12 October 2026.
1. An owner proposes a candidate
The owner first uploads KYC to the contract, then proposes a node with a stake of at least 10 million XDC. From that moment the node is a masternode candidate. Owners apply through the official XinFin Masternode dashboard, as the XDC docs describe.
2. Holders can add votes
Any address can add XDC to a candidate's stake with the contract's vote function, at least 25,000 XDC per vote. Votes count towards the candidate's total stake. The official pages we checked do not describe how voters are rewarded, so ask the node's operator before you vote.
3. The 108 largest stakes become validators
At each epoch switch the node software sorts all candidates by total stake (the owner's stake plus votes), removes the ones under penalty and takes the first 108 as masternodes. The remaining candidates are the standby nodes (XDPoSChain source code).
4. Validators take turns producing blocks
Within an epoch, validator nodes create blocks in turn (XDC docs, XDPoS). A block is final once three more blocks confirm it, about six seconds at the ~2-second block time, and the protocol is designed to withstand up to one third of validators acting maliciously (xdc.org).
5. Rewards are paid per epoch
An epoch is 900 blocks. On chain, masternode owners are paid 4,500 XDC per epoch in total, about 41.7 XDC per masternode (measured by our masternode rewards checker); xinfin.org quotes 6,000 XDC per epoch as an illustrative figure, and states that protector and observer rewards are currently paid from the XDC Ecosystem Reward Wallet (xinfin.org). The tiers and a worked example are on our masternodes page.
Penalties: why a validator leaves the active set
The rules below are from the XDC documentation on slashing and the validator contract.
Missing a whole epoch
A masternode that fails to sign any block during an entire epoch is excluded from block production for the next four epochs. If several masternodes underperform in the same epoch, each gets the same penalty. The set keeps producing blocks with the remaining validators.
Earning nothing while penalised
A penalised masternode can still verify and sign blocks, but it is not eligible for rewards during the penalty. If it resumes signing, it can return to normal operation without a permanent penalty. The slashing page does not describe any loss of stake for downtime.
Provable misbehaviour
Beyond downtime, XDC 2.0 includes a forensic system that can identify malicious nodes with proof (xdc.org).
Leaving on purpose
An owner who resigns a candidate must wait 1,296,000 blocks, about 30 days, before the stake can be withdrawn; xinfin.org also states 30 days (xinfin.org). A voter who withdraws a vote waits 432,000 blocks, about 10 days. Both delays are set in the validator contract.
How to check an XDC validator yourself
- Copy the address from the table with its Copy button.
- Open it on a block explorer. The XDCScan link in each row shows the address, its balance and its transactions.
- Look it up on the official dashboard. The XinFin Masternode dashboard is where owners apply, stake and manage their nodes.
- Ask the chain directly. Send the JSON-RPC method XDPoS_getMasternodesByNumber with the parameter latest to a public XDC RPC endpoint, such as those in the XDC RPC documentation. The reply lists the masternodes, the standby nodes and the penalised nodes, with counts in the fields MasternodesLen, StandbynodesLen and PenaltyLen.
If the counts on this page differ slightly from another site, check the time: the set changes at every epoch switch, and our table refreshes every 10 minutes.
Is XDC decentralized?
It depends on what you measure. Becoming a candidate is open to anyone who can stake 10 million XDC and upload KYC, and the active set is chosen by a fixed rule in the node software, not by a company. But only 108 masternodes produce blocks at any time, every owner must pass KYC, and the set is ranked by stake, so large holders and their voters decide which nodes make it in.
The chain shows addresses, not owners. One operator can run several masternodes, and operator names are not on-chain, so counting addresses is not the same as counting independent operators. Treat any claim that a named company runs a given node as unconfirmed unless the company says so itself.
Some companies have said so. MoneyGram announced on 15 October 2026 that it is joining as an institutional validator; MoneyGram joins XDC as a validator sets out what it said and what it has not disclosed yet, such as how many nodes it will run and when.
Can you mine XDC?
No. XDC has no mining with graphics cards or ASICs: blocks are produced by masternodes under XDPoS, a proof-of-stake design (XDC docs). New XDC reaches validators as epoch rewards instead; the effect on supply is on our XDC supply page. Apps or websites that offer “XDC cloud mining” are not part of the network.
Common mistakes and safety
- Sending XDC to a validator address to “stake”. A plain transfer to a masternode address is not a stake or a vote. Staking and voting happen through the validator contract, usually via the official dashboard or a staking provider.
- Reading an address as a company. The chain shows no operator names. Only trust an operator's identity if the operator publishes it.
- Forgetting the waiting period. Resigning a masternode locks the stake for about 30 days, and withdrawing a vote for about 10 days.
- Believing guaranteed returns. Rewards depend on uptime, on the reward rules and on the XDC price. No one can promise a fixed income.
- Fake masternode services. No legitimate service needs your recovery phrase to set up or manage a node. More in the safety center.
XDC validators FAQ
Up to 108 active masternodes produce blocks at any time, with further candidates on standby. The live counts are at the top of this page.
Yes. XDC uses XDPoS 2.0, a delegated proof-of-stake consensus in which the 108 candidates with the largest stake produce and confirm blocks.
No. There is no proof-of-work mining on XDC. Blocks are produced by staked masternodes, which receive the rewards.
A masternode (validator) candidate needs at least 10 million XDC, plus KYC and a server that stays online. See the masternode guide.
A node's owner uploads KYC and proposes it with at least 10 million XDC. At each epoch switch, the 108 candidates with the largest total stake (own stake plus votes) that are not under penalty become the active validators.
The validator contract lets any address add at least 25,000 XDC to a candidate's stake as a vote. Withdrawing a vote takes about 10 days. The official pages do not describe voter rewards, so ask the operator first.
A masternode that signs no block during a whole epoch is excluded from block production for the next four epochs and earns no rewards in that time. Source: XDC docs, slashing.
About 30 days after the owner resigns. The validator contract holds a resigned stake for 1,296,000 blocks before it can be withdrawn.
Partly. Anyone with 10 million XDC and KYC can become a candidate, but only 108 masternodes produce blocks, ranked by stake, and operator names are not on-chain.
The chain only shows addresses, not owners, and one operator can run several masternodes. We do not attribute a node to a company unless that company says so itself.