Block height
258,677
Age of last block: 28 s
At least one value is critical. See the details below.
Data as of 2026-10-25 17:40 UTC
Block height
258,677
Age of last block: 28 s
Average block interval (24 h)
84 s
OK
Reorgs (7 days)
0
Active signers (100 blocks)
2
Warning
Largest producer (100 blocks)
24.0%
OK
Verified full-history nodes
6
OK
MatMul rate (7 days)
215.0 M/s
Next halving
266,323
Notable changes of the last 30 days, newest first - reorgs, long pauses between blocks, disagreement of the explorers, new releases and signers that stopped or started signing. Detected by this page while collecting.
Number of blocks in the chain. It should rise steadily, about every 90 seconds.
Not enough data for this time range yet.
Time since the newest block was found. Long pauses can mean that mining has stalled.
Not enough data for this time range yet.
Average time between two blocks over the last day. The target is 90 seconds.
Not enough data for this time range yet.
The longest pause between two blocks during the last day.
Not enough data for this time range yet.
Number of blocks found during the last day. About 960 are expected.
Not enough data for this time range yet.
How often the chain switched to a competing branch during the last week.
Not enough data for this time range yet.
The largest number of blocks that were replaced in one reorg during the last week.
Not enough data for this time range yet.
Reorgs detected by our node in the last 30 days, newest first, with the height where the chains split and how many blocks were replaced.
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.
Tip height of each source, how many blocks it is behind our node (negative = ahead), the compared block a few blocks below its tip and whether its hash matches the one of our node. No verdict means our node does not have that block yet.
| Source | Tip | Lag (blocks) | Block | Hash (start) | Matches our node |
|---|---|---|---|---|---|
| btxscan explorer | 258,684 | -7 | 258,678 ↗ btxscan ↗ Byron Bay | b529b11be8b56c82 | – |
| Byron Bay explorer | 258,690 | -13 | 258,684 ↗ btxscan ↗ Byron Bay | d7d8b296fea71bbd | – |
| easyBTX census | 258,690 | -13 | 258,684 ↗ btxscan ↗ Byron Bay | d7d8b296fea71bbd | – |
Number of other valid chain branches the node currently sees next to the main chain.
Not enough data for this time range yet.
Warnings the node reports about signed blocks and chain selection. Normally there are none.
Not enough data for this time range yet.
Combined check that there are no warnings, the node is fully synced and its peers agree on the same tip.
How many announced blocks the node has not yet fully processed. Should be 0 or 1.
Not enough data for this time range yet.
Disk space needed to store the complete blockchain.
Not enough data for this time range yet.
How hard it currently is to find a block. It adjusts automatically to the mining power.
Not enough data for this time range yet.
Chain-inferred work-equivalent rate over the last day. A protocol normalisation, not raw computing power.
Not enough data for this time range yet.
Chain-inferred work-equivalent rate over the last week.
Not enough data for this time range yet.
Number of different payout addresses among the last 1,000 blocks.
Not enough data for this time range yet.
The smallest number of producers that together found more than half of the last 1,000 blocks. The higher, the more decentralised.
Not enough data for this time range yet.
Producers with their number of blocks and share. Names come from a maintained list; unknown ones are shown shortened.
| Producer | Payout address | Blocks | Share (%) |
|---|---|---|---|
| – | btx1zfnf…q9vr ↗ btxscan ↗ Byron Bay | 240 | 24 |
| – | btx1z6rq…efrr ↗ btxscan ↗ Byron Bay | 170 | 17 |
| – | btx1zkjd…fdz0 ↗ btxscan ↗ Byron Bay | 110 | 11 |
| – | btx1zj00…8yvn ↗ btxscan ↗ Byron Bay | 80 | 8 |
| – | btx1zr4d…ukj9 ↗ btxscan ↗ Byron Bay | 60 | 6 |
Number of signer keys that signed blocks recently. Trusted mirrors need signatures from at least two.
Not enough data for this time range yet.
Per signer key the operator (if known), signed blocks out of the last 100 and when it was last seen.
| Signer key | Operator | btxscan witness (last 100) | easyBTX witness (last 100) | Pinned by our node |
|---|---|---|---|---|
| 02d5efca…4675 | Mende/Junior (easyBTX) | 88 | 100 | Yes |
| 037db271…c804 | – | 99 | – | Yes |
| 02d12c32…e030 | Jarek (Byron Bay) | – | – | Yes |
How many of the active signers have a publicly known operator.
Not enough data for this time range yet.
Whether our archive node receives enough signatures to accept new blocks.
Number of the last 100 blocks that did not receive the two required signatures.
Number of other nodes our archive node is connected to.
Not enough data for this time range yet.
How many of our node's peers are at the current tip of the chain.
Not enough data for this time range yet.
Number of nodes in the network that accept connections.
Not enough data for this time range yet.
Distribution of the node software versions in the network.
| Version | Nodes |
|---|---|
| BTX:0.34.15 | 18 |
| BTX:0.32.12 | 9 |
| BTX:0.34.12 | 2 |
| BTX:0.33.2 | 2 |
| BTX:0.34.4 | 1 |
| BTX:0.32.11 | 1 |
| BTX:0.31.0 | 1 |
| BTX:0.34.9 | 1 |
| BTX:0.32.3 | 1 |
Nodes that announce that they store the complete blockchain.
Not enough data for this time range yet.
Nodes that actually delivered an old block when tested. New nodes need them to sync.
Not enough data for this time range yet.
Full-history nodes that are also fully synced.
Nodes that stopped following the main chain.
Not enough data for this time range yet.
Nodes running an outdated software version.
Not enough data for this time range yet.
Known public archive nodes and their status. Only archives that published their address themselves are listed.
Amount of BTX issued through mining so far.
Not enough data for this time range yet.
Coins not issued through mining. The BTX protocol has no premine or dev allocation (source code, chainparams.cpp).
Not enough data for this time range yet.
Total amount of BTX in circulation.
Not enough data for this time range yet.
Circulating supply as a share of the maximum of 21 million BTX.
Not enough data for this time range yet.
New BTX created with each block. It halves every 525,000 blocks.
Not enough data for this time range yet.
Blocks remaining until the block reward halves.
Not enough data for this time range yet.
Number of transactions during the last day.
Not enough data for this time range yet.
Total transaction fees paid during the last day.
Not enough data for this time range yet.
Transactions waiting to be included in a block.
Not enough data for this time range yet.
Newest official release of the BTX node software on GitHub.
Software version of our archive node.
Share of nodes running the newest release.
Not enough data for this time range yet.
Days until all clients from v0.30.0 stop working (6 Nov 2028) unless a new release extends the date.
Not enough data for this time range yet.
Scheduled protocol changes and the blocks remaining until they activate.
Time when the data on this page was generated.
For each data source whether it is reachable and when data was last received.
| Source | Detail | OK | Missing values | Data from |
|---|---|---|---|---|
| Own archive node | – | Yes | 0 | 2026-10-25 17:40 UTC |
| GitHub | btxchain/btx releases | Yes | – | 2026-10-25 17:36 UTC |
| easyBTX witness | – | Yes | – | 2026-10-25 17:36 UTC |
| btxscan witness | – | Yes | – | 2026-10-25 17:36 UTC |
| easyBTX census | network | Yes | – | 2026-10-25 17:36 UTC |
| easyBTX census | nodes | Yes | – | 2026-10-25 17:36 UTC |
| Byron Bay explorer | supply | Yes | – | 2026-10-25 17:36 UTC |
| btxscan explorer | block check | Yes | – | 2026-10-25 17:36 UTC |
| Byron Bay explorer | block check | Yes | – | 2026-10-25 17:36 UTC |
| GitHub | btxchain/btx | Yes | – | 2026-10-25 16:41 UTC |
| GitHub | MendeMatthias/easynode | Yes | – | 2026-10-25 16:41 UTC |
Version of this status page software.
Time since the last data delivery from our archive node.