BTX Network Status

Incident

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.

  1. Signer Mende/Junior (easyBTX) started signing
  2. Explorers agree with our node again
  3. Explorers show a different block than our node
  4. Reorg: 1 block(s) replaced from height 255,100 ↗ btxscan ↗ Byron Bay
  5. No block for 36 min before height 249,400 ↗ btxscan ↗ Byron Bay
All events of the last 30 days
  1. New release v0.34.15
Block height
What does this mean?

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

258,677 ↗ btxscan ↗ Byron Bay
History
Age of last block
What does this mean?

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

28 s OK
History
Average block interval (24 h)
What does this mean?

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

84 s OK
History
Longest gap (24 h)
What does this mean?

The longest pause between two blocks during the last day.

7 min 50 s OK
History
Blocks (24 h)
What does this mean?

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

1,032
History
Reorgs (7 days)
What does this mean?

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

0
History
Deepest reorg (7 days)
What does this mean?

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

0 OK
History
Recent reorgs
What does this mean?

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.

No entries.
Explorers agree
What does this mean?

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.

– Unknown
Explorer comparison
What does this mean?

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: Own archive node, btxscan explorer, Byron Bay explorer, easyBTX census
SourceTipLag (blocks)BlockHash (start)Matches our node
btxscan explorer258,684-7258,678 ↗ btxscan ↗ Byron Bayb529b11be8b56c82–
Byron Bay explorer258,690-13258,684 ↗ btxscan ↗ Byron Bayd7d8b296fea71bbd–
easyBTX census258,690-13258,684 ↗ btxscan ↗ Byron Bayd7d8b296fea71bbd–
Competing chains
What does this mean?

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

0 OK
History
Finality warnings
What does this mean?

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

0 OK
History
Fork check
What does this mean?

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

Yes OK
Header lag
What does this mean?

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

0 OK
History
Chain size
What does this mean?

Disk space needed to store the complete blockchain.

140.2 GB
History
Difficulty
What does this mean?

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

1.8 G
History
MatMul rate (1 day)
What does this mean?

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

208.4 M/s
History
MatMul rate (7 days)
What does this mean?

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

215.0 M/s
History
Largest producer (100 blocks)
What does this mean?

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

24.0% OK
History
Largest producer (1,000 blocks)
What does this mean?

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

21.3% OK
History
Distinct producers (1,000 blocks)
What does this mean?

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

37
History
Nakamoto coefficient (1,000 blocks)
What does this mean?

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

Source: Own archive node
3 OK
History
Block producers
What does this mean?

Producers with their number of blocks and share. Names come from a maintained list; unknown ones are shown shortened.

Source: Own archive node, producer list
ProducerPayout addressBlocksShare (%)
–btx1zfnf…q9vr ↗ btxscan ↗ Byron Bay24024
–btx1z6rq…efrr ↗ btxscan ↗ Byron Bay17017
–btx1zkjd…fdz0 ↗ btxscan ↗ Byron Bay11011
–btx1zj00…8yvn ↗ btxscan ↗ Byron Bay808
–btx1zr4d…ukj9 ↗ btxscan ↗ Byron Bay606
Active signers (100 blocks)
What does this mean?

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

Source: btxscan witness, easyBTX witness
2 Warning
History
Signers
What does this mean?

Per signer key the operator (if known), signed blocks out of the last 100 and when it was last seen.

Source: btxscan witness, easyBTX witness, Own archive node, signer list
Signer keyOperatorbtxscan witness (last 100)easyBTX witness (last 100)Pinned by our node
02d5efca…4675Mende/Junior (easyBTX)88100Yes
037db271…c804–99–Yes
02d12c32…e030Jarek (Byron Bay)––Yes
Active signers with known operator
What does this mean?

How many of the active signers have a publicly known operator.

Source: btxscan witness, easyBTX witness, signer list
1 Critical
History
Own mirror quorum
What does this mean?

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

Yes OK
Blocks without quorum (100 blocks)
What does this mean?

Number of the last 100 blocks that did not receive the two required signatures.

Planned (phase 3)
Peers of our node
What does this mean?

Number of other nodes our archive node is connected to.

12
History
Synced peers
What does this mean?

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

6
History
Reachable nodes
What does this mean?

Number of nodes in the network that accept connections.

Source: easyBTX census
36
History
Software versions
What does this mean?

Distribution of the node software versions in the network.

Source: easyBTX census
VersionNodes
BTX:0.34.1518
BTX:0.32.129
BTX:0.34.122
BTX:0.33.22
BTX:0.34.41
BTX:0.32.111
BTX:0.31.01
BTX:0.34.91
BTX:0.32.31
Nodes advertising full history
What does this mean?

Nodes that announce that they store the complete blockchain.

Source: easyBTX census
9
History
Verified full-history nodes
What does this mean?

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

Source: easyBTX census
6 OK
History
Full history and at tip
What does this mean?

Full-history nodes that are also fully synced.

Planned (phase 3)
Stranded nodes
What does this mean?

Nodes that stopped following the main chain.

Source: easyBTX census
0
History
Outdated nodes
What does this mean?

Nodes running an outdated software version.

Source: easyBTX census, GitHub
18
History
Public archives
What does this mean?

Known public archive nodes and their status. Only archives that published their address themselves are listed.

Planned (phase 3)
Mined supply
What does this mean?

Amount of BTX issued through mining so far.

5,173,540 BTX
History
Other allocations
What does this mean?

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

0 BTX
History
Circulating supply
What does this mean?

Total amount of BTX in circulation.

5,173,540 BTX
History
Share of maximum supply
What does this mean?

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

24.6%
History
Block reward
What does this mean?

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

20 BTX
History
Next halving
What does this mean?

Blocks remaining until the block reward halves.

266,323
History
Transactions (24 h)
What does this mean?

Number of transactions during the last day.

2,580
History
Fees (24 h)
What does this mean?

Total transaction fees paid during the last day.

0.10689728 BTX
History
Mempool
What does this mean?

Transactions waiting to be included in a block.

3
History
Latest release
What does this mean?

Newest official release of the BTX node software on GitHub.

Source: GitHub
v0.34.15
Our node version
What does this mean?

Software version of our archive node.

v0.34.15
Adoption of latest release
What does this mean?

Share of nodes running the newest release.

Source: easyBTX census, GitHub
50.0%
History
Client expiry
What does this mean?

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

743 days OK
History
Upcoming activations
What does this mean?

Scheduled protocol changes and the blocks remaining until they activate.

No entries.
Data generated at
What does this mean?

Time when the data on this page was generated.

2026-10-25 17:41 UTC
Data sources
What does this mean?

For each data source whether it is reachable and when data was last received.

SourceDetailOKMissing valuesData from
Own archive node–Yes02026-10-25 17:40 UTC
GitHubbtxchain/btx releasesYes–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 censusnetworkYes–2026-10-25 17:36 UTC
easyBTX censusnodesYes–2026-10-25 17:36 UTC
Byron Bay explorersupplyYes–2026-10-25 17:36 UTC
btxscan explorerblock checkYes–2026-10-25 17:36 UTC
Byron Bay explorerblock checkYes–2026-10-25 17:36 UTC
GitHubbtxchain/btxYes–2026-10-25 16:41 UTC
GitHubMendeMatthias/easynodeYes–2026-10-25 16:41 UTC
Monitoring version
What does this mean?

Version of this status page software.

0.1.0
Age of node data
What does this mean?

Time since the last data delivery from our archive node.

66 s OK