Tesseracoin Explorer

Consensus

Parameters of the active era at the tip, and the history of on-chain activations that have changed them. Eras are added via consensus_activation txs — every honest validator enforces the activated params at and beyond the activation height. Activations are sequential replacements, not stacked: at any given height exactly one authority is in effect (the most recent activation ≤ that height).

Active era

Era adoption & pending activations

Upcoming consensus-era changes and whether each node is ready for them. A network switches eras one of two ways: an owner-multisig consensus_activation tx (manual governance — not a stakeholder vote), or — on a ladder network — an automatic promotion that fires the moment its work / stake / dwell bonds are met (activated_by=auto, no owner signature). Either way it commits at a fixed activation height (the ETA estimates that from observed cadence). Any node missing the new era's code rejects the block and forks off at that height — this catches such a "ticking fork" before it happens. An auto-promotion appears in the table below only once its bonds are met (scheduled SAFETY_WINDOW blocks ahead); the Next automatic promotion panel tracks the bond progress before that, so a ladder flip is never a surprise.

Upcoming activations

Per-node readiness (for the next activation)

Difficulty & block cadence

Observed block time per block over the recent window, against the era's target_block_time (dashed line). Difficulty retargets every block via LWMA-1, so a persistent gap closes within a few blocks as it tracks the real hash rate. Work per block = the expected number of hash attempts to mine a block (2256 ÷ target), so a rising line = harder — the same unit shown next to initial_target in the params below.

Active params

Activation history

Each row is one era. "Overrides" lists the fields whose values changed from the prior era — that's exactly what the activation rewrote.

Locally-registered authorities

Authority plugins this node has Python code for. Only one is active at a time (see above); the rest are dormant — available to validate blocks if/when an activation switches the chain to them. An empty description means the authority class doesn't carry a docstring yet.