Network Status
Checked Nov 13, 2026, 07:37:51 UTCHEALTHYSafe to send
BTX network is healthy.
The last block was 3 minutes ago. Normal target is 90 seconds.
3m 29s
since the last block, #276,534, mined Nov 13, 2026, 07:34:22 UTC. 2 blocks missed against the 90 second target.
Independent source agrees
Our server’s own check
checked 7 mins agoVerdict
ON THE NETWORK'S CHAIN
Our node
#276,529 6d32687825…6fc384
The network
#276,529, backed by our own chain
Attested tip
#276,534
The signed frontier. Every balance here is read at this height.
Proof of work tip
#276,534
Highest block mined, per btx-pool. Mined is not attested.
Gap
0
Nothing mined above the signed frontier.
What each source says
hash compared at #276,525| Source | Height | Hash | Tip age | Agreement |
|---|---|---|---|---|
Our nodethis site The source every balance and transaction on this site is read from. | 276,534attested tip | 47f30979db…dc08d0 | 3 mins ago | reference |
The only witness that publishes block hashes, so the only one that can settle a fork. | 276,531attested tip | fe232ae522…6dd7bc | 7 mins ago | agrees |
Template height minus one. Weakest witness, never usable alone. | 276,534template height, tip + 1 | not published | not published | no hash published |
Measures the tip from many nodes' own headers, so it can see a split that a single explorer cannot. | 276,534mined tip | not published | not published | agrees |
- Byron esplora is a witness only. Never use it for a balance. Its address index under-reports spends: 507 BTX of balance that was already spent showed on a single address when we measured it on 2026-08-19. For a block hash at a known height it is the best independent check we have, because it is the only one that publishes hashes.
- btx-pool is a witness only, and the weakest one. Its published height is a TEMPLATE height, one above its tip, so the number shown here is that value minus one. During the August stall it tracked an unattested fork and reported 199,310 while the attested tip was 199,297. Never use it for a balance and never use it alone.
- The easyBTX node census is a survey, not a server. It asks every reachable BTX node for its own block headers, so it can see a split that no single explorer can: on 2026-09-05 it correctly reported a heavier branch 426 blocks above the one this site was following, while our only hash-publishing witness sat about 200 blocks stale. It publishes aggregates and a short prefix of each branch’s tip hash, never balances, and it runs every half hour rather than continuously.
Recent block intervals
target 1m 30snow3m 29sopen
#276,5341m 59s
#276,53327s
#276,5321m 13s
#276,5311m 30s
#276,5301m 12s
#276,52956s
#276,52827s
#276,52720s
#276,5262m 12s
Block timestamps are set by miners and are not strictly monotonic, so an interval can come back out of order.
Consensus
Releases ↗Version to run
v0.34.15 (nothing older than v0.34.14 follows the chain)
Upgrading from 0.34.13 or older: an unset -reorgpolicy now means legacy. Set -reorgpolicy=bounded to keep the behaviour you had.
Upcoming activation
None pending. Past ones are listed below.
Earlier activations
#244,000 v0.34.14, three checks (32-byte HTLC preimage, recovery proofs count toward the shielded block budget, a MatMul header that only passed the quick precheck cannot be the best header); older nodes can follow a branch the network refuses, 2026-10-10
#199,299 v0.33.4 through v0.34.1, nMatMulStallRecoveryHeight, PUBLISHED 2026-08-24 and WITHDRAWN 2026-08-27. Nodes on those builds stop here, 2026-08-24
#191,714 v0.33.3, MatMul ASERT difficulty floor, 2026-08-17
#185,000 v0.33.2, required upgrade gate
Builds on the network
Live version split ↗ from the easyBTX node census
A node on an old build does not stop with an error. It parks short of the activation, or, as at #244,000, keeps following a branch the rest of the network refused, and answers as though nothing is wrong. That is the failure this page is built to make visible.
Ages are measured against the wall clock, not against another endpoint. This page refreshes at least every 30 seconds. Witness sources are cross-checks on the chain tip and must never be read for a balance.