| Validators | Self-bond | Delegators | Delegated | Total | Reward Cap |
|---|---|---|---|---|---|
| 0 | 0 FLR | 0 | 0 FLR | 0 FLR | 0 FLR |
| All validators — per-node metrics | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Provider↑ | ReliabilityWindow: 26 epochs (~90 days). Base: 100. −1 per strike. Ineligible or not registered: (1+2+…+n)×5 for the nth consecutive miss. Terminal validators: −100 × (bricked / total). | Node ID | Total Stake | Cap | Free Space | Fee | AV. APR | Delegators | Start | End | Time Left | Uptime | Ver | |
See how validator staking and FTSO delegation rewards compare for your FLR amount.
Compare Rewards→Data provided by Flare Metrics.
Evaluating a validator on Flare involves looking at more than just total stake. Uptime, time left in the current staking period, delegation fees, and how close a validator is to key caps all affect both security and potential rewards. On this page, Flare Builders surfaces self-bonded stake, delegated stake, free space, delegator counts, version information, and whether each node is currently connected. You can sort by any of these columns to build a shortlist of validators that match your preferences.
As a delegator, it is often sensible to prefer validators with strong uptime, up-to-date software, and capacity remaining rather than those that are already near reward caps. Diversifying across multiple well-performing validators can also reduce the impact if a single operator experiences issues or changes their fee policy.