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 our node switched to a competing branch during the last week. Switches at the same fork height within 10 minutes count once (one race, even if the node flipped back and forth).

The largest number of blocks that were replaced in one reorg during the last day. Short reorgs settle by themselves; after 24 hours a reorg no longer counts for the traffic light, but it stays in the list of recent reorgs.

The largest number of blocks that were replaced in one reorg during the last week. For information only; the traffic light uses the last 24 hours.

The public block explorers (btxscan, Byron Bay) and the easyBTX node census show the same block as our node at a settled height a few blocks below their tip. If not, someone is on a different chain or an explorer has a problem.

Of all answers counted above (block height and chain), the share that matches our node. Its history shows how often the sources agreed in the past.

Number of other valid chain branches the node sees right now next to the main chain. Two branches for a minute are a normal race that settles by itself, so this value has no traffic light; the light is on the value for 15 minutes.

The number of competing chain branches that lasted for the whole last 15 minutes (the lowest value of that time). A short race does not count, a lasting split does.

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. In BTX 0.34.15 they stay until the node restarts, even when the cause is long over, so they are shown for information only and do not change the traffic light. Real forks show up in the fork check and the reorg values.

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. Above 50 % it is critical, unless the producer is a known pool of many miners - then it is a warning, because the miners can switch pools.

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. A value of 1 is critical, unless that producer is a known pool of many miners - then it is a warning.

Number of signer keys that signed blocks recently. Trusted mirrors need signatures from at least two, so two active signers are enough (green); the missing spare is explained below the value.

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.

Connections of our two archive nodes to peers more than 1,000 blocks below the tip - nodes that are stuck or still syncing. Counted per connection; no node is named.

Start a new node in minutes: a pruned datadir, published daily and checked twice - in an offline node here, then by our second archive, which signs it. Verify with key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFr6GHJapBKdUdEDuyIQpzE8rGrdZ73rWWtKxoO71FaY

Time since the latest signed snapshot was published. A new one comes every day; older than about two days means the snapshot pipeline needs a look.

BTX actually paid out as block rewards so far. Explorers show 20 BTX × block height; this value is 9,461.25 BTX lower because 783 blocks without transactions between heights 130,000 and 131,999 received less than the full 20 BTX (rule against empty blocks).

All spendable transparent coins in the UTXO set of our second archive node at its tip, computed by the node itself (gettxoutsetinfo). Coins in the shielded pool are not part of it. The figure of Byron Bay (which includes the shielded pool) is the reference.

The block the UTXO set above belongs to; at most 10 blocks below our tip.

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

BTX issued so far 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, and the estimated month at the block pace of the last 24 hours.

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.

Share of the peer connections of our two archive nodes that run the newest release - our own measurement. The easyBTX census above is the reference; both views differ a little because they see different nodes.

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 is up to date - at most 3 blocks behind the public explorers, the block signed by the signers on its chain, and no header-only branch more than 6 blocks above it. Until it is, verdicts that depend on it are paused, and the block height shown comes from btxscan and Byron Bay while both agree.

Whether all of our archive nodes deliver data, are up to date and follow the same chain. If one is stuck, the page values come from the other one.

Version of this status page software. What changed in each version is listed on the Changes page.

Time since the last data delivery from our archive node.