Pixapixa.org — developer resources

Activity

Who is producing blocks, how healthy the network is, and what changed in the code this week. Your browser reads all of it directly — the chain from a public node, the code from GitHub — and nothing here is stored anywhere else.

Contents

Network

Loading from the node…

Reading the chain…

The last 128 slots, oldest on the left. Filled: a block was produced. Empty: the slot was missed.

Chain

Schedule

Witnesses take turns in a round that is reshuffled every 21 blocks. The order below is the current round; the filled name is producing this block and the dashed one is next.

Witnesses

Votes weigh by the voter's VESTS, and each account can vote for thirty witnesses, so shares do not add up to one stake. Missed blocks only ever grow; the two right-hand counts are computed from samples this page took itself, in this browser. Click a column to sort, a row to see every raw field.

# Witness Votes, VESTS Missed 1 h / 24 h Last block Feed Version Findings
Loading…

Recent blocks

The last 300 blocks, oldest on the left, shaded by producer. A gap marks a missed slot: the round moved on without a block.

Health findings

The same rules the witness-status command-line check applies, so what you see here is what a cron job would page you for. Info is worth knowing, warn is worth a look, critical is worth a call.

  • Waiting for the first sample.

How this is computed

One JSON-RPC batch to the selected node returns the dynamic global properties, the witness schedule, every witness object, the feed history, the hardfork properties and the node version; a second one fetches the witness accounts and the vote list; a third fetches the recent blocks. Head age is your clock against the block's timestamp, so a computer with a wrong clock sees false lagging. Missed slots all time is current_aslot − head_block_number; participation is participation_count / 128; a witness is disabled when its signing key is the null key; a feed is stale after seven days. The full set of formulas and thresholds is in AGENT.md, and a bot that wants the same figures without a browser can read status.json, regenerated every ten minutes.

Latest on GitHub

Public events across the pixagram-blockchain organisation: pushes with their commit messages, releases, new repositories, issues and pull requests. GitHub allows sixty anonymous requests an hour from one address, so this list refreshes only when you reload the page.

  • Loading…

Repositories

Every public repository of the organisation, most recently pushed first.

RepositoryDescriptionLanguageLast push
Loading…