Degraded

Number of blocks in the chain. It should rise steadily, about every 90 seconds.

Time since the newest block was found. Long pauses can mean that mining has stalled.

Average time between two blocks over the last day. The target is 90 seconds.

The longest pause between two blocks during the last day.

Number of blocks found during the last day. About 960 are expected.

How often the chain switched to a competing branch during the last week.

The largest number of blocks that were replaced in one reorg during the last week.

Number of other valid chain branches the node currently sees next to the main chain.

Warnings the node reports about signed blocks and chain selection. Normally there are none.

Combined check that there are no finality warnings, the node is fully synced and its peers agree on the same tip.

Warnings our node reports, e.g. after a short race of two branches. They stay until the node restarts, even when the cause is over, so they are a warning, not an incident.

How many announced blocks the node has not yet fully processed. Should be 0 or 1.

Disk space needed to store the complete blockchain.

How hard it currently is to find a block. It adjusts automatically to the mining power.

Chain-inferred work-equivalent rate over the last day. A protocol normalisation, not raw computing power.

Chain-inferred work-equivalent rate over the last week.

Share of the last 100 blocks found by the single largest producer. High values mean centralisation.

Share of the last 1,000 blocks found by the single largest producer.

Number of different payout addresses among the last 1,000 blocks.

The smallest number of producers that together found more than half of the last 1,000 blocks. The higher, the more decentralised.

Number of signer keys that signed blocks recently. Trusted mirrors need signatures from at least two.

How many of the active signers have a publicly known operator. This is transparency information, not a health check, so it has no traffic light and does not affect the overall status.

Whether our archive node receives enough signatures to accept new blocks.

Number of other nodes our archive node is connected to.

How many of our node's peers are at the current tip of the chain.

Number of nodes in the network that accept connections.

Nodes that announce that they store the complete blockchain.

Nodes that actually delivered an old block when tested. New nodes need them to sync.

Nodes that stopped following the main chain.

Nodes running an outdated software version.

Amount of BTX issued through mining so far.

Coins not issued through mining. The BTX protocol has no premine or dev allocation (source code, chainparams.cpp).

Total amount of BTX in circulation.

Circulating supply as a share of the maximum of 21 million BTX.

New BTX created with each block. It halves every 525,000 blocks.

Blocks remaining until the block reward halves.

Number of transactions during the last day.

Total transaction fees paid during the last day.

Transactions waiting to be included in a block.

Newest official release of the BTX node software on GitHub.

Software version of our archive node.

Share of nodes running the newest release.

Days until all clients from v0.30.0 stop working (6 Nov 2028) unless a new release extends the date.

Time when the data on this page was generated.

Whether our archive node has caught up with the network (at most 3 blocks behind the public explorers). Until it has, values from the node may be outdated and the comparison with other services is paused.

Version of this status page software.

Time since the last data delivery from our archive node.