0 — usually the error / restart counter. Zero is good…
0 reactions
0 — usually the error / restart counter. Zero is good.
51,642,648 — that's the network's current DAG height (total transactions the network has seen). Millix isn't a chain of blocks, it's a DAG, so this number just keeps climbing as new transactions get woven in.
6 peers — you're connected to 6 other nodes right now. That's low — community reports this year show 80/128 peers on a stable node in Week 14, and 130 active peers back in April. More peers = faster validation and more fee opportunities.
1,032 millix events — almost certainly the auto-consumption events your node has generated or verified. Millix forces every unspent older than 10 minutes to hibernate, and nodes automatically create 0b0 transactions to refresh them. Those self-sends are counted as "events" in most node UIs.
0 backlog — perfect. Your node is fully synced, no transactions waiting to be processed.
42,479 transactions — total transactions your node has validated (or seen and stored) since it started.
51,642,648 — that's the network's current DAG height (total transactions the network has seen). Millix isn't a chain of blocks, it's a DAG, so this number just keeps climbing as new transactions get woven in.
6 peers — you're connected to 6 other nodes right now. That's low — community reports this year show 80/128 peers on a stable node in Week 14, and 130 active peers back in April. More peers = faster validation and more fee opportunities.
1,032 millix events — almost certainly the auto-consumption events your node has generated or verified. Millix forces every unspent older than 10 minutes to hibernate, and nodes automatically create 0b0 transactions to refresh them. Those self-sends are counted as "events" in most node UIs.
0 backlog — perfect. Your node is fully synced, no transactions waiting to be processed.
42,479 transactions — total transactions your node has validated (or seen and stored) since it started.
| 4,000 mlx | |
| 10 | |
| 0 |