Height
0
chain block number, 0 blocks in the DAG
The devnet
The devnet explorer.
Every block the devnet made in the last day and every transaction of the last seven days, read from a node by the observer and the indexer. Paste a block hash, a transaction hash, a chain block number or an address, or click any row. The devnet is a test network: its coins have no value and the chain may reset. Every number here comes from one node on the build box, the chain the finality certificates follow; the indexer reads that node's execution RPC and nothing else.
Status
OFFLINE
no observer update yet
DAA score
0
blue score 0
Hash rate
0
difficulty 0
Chain rate, 10 min
0blocks/s
DAG blocks per second; chain blocks per second
Finality
n/a
voters and weight
Program class
v4
the hash program family at the tip
Proving
0paid
shards paid in the last 10 min for blocks of any age
The DAG
the newest 150 blocks, one lane per miner
chain blockblue, mergedred, excludedpending◆ under a lock● every shard paid
Left to right is arrival order at the observer; a line joins a block to each parent in the picture. Blue blocks are merged and paid; red blocks are excluded from the order. A diamond outline marks a block under a finality lock, a filled dot a block whose every planned shard has been paid. Click a block for its page.
Latest blocks
newest first, every 5 s
| Block | Number | DAA | Blue score | Class | Miner | Txs | Shards paid | Final | Time |
|---|---|---|---|---|---|---|---|---|---|
| Loading. | |||||||||
chain blockblue, merged and paidred, excludedpending, not merged yet★ locked checkpoint
Number is the chain block number, the same number the EVM reports; a block off the selected chain has none. Class is the hash program family the block was mined under. Txs is what the block carries; the EVM executes each transaction once, in the first chain block that includes it. Shards paid counts the block's proof shards a later coinbase has paid. Final means a finality lock covers the block.
Latest transactions
newest first, every 5 s
| Transaction | Block | From | To | Value | Status | Time |
|---|---|---|---|---|---|---|
| Loading. | ||||||
EVM transactions as the indexer read them from the node's receipts: seven days are kept. Value is in IGN (18 decimals on the EVM side).
Proving
shards, provers, latency
The proving view: every chain block's shard plan, who proved what, and the block-to-paid latency.
Public API
JSON, cached 5 to 10 s
- /api/stats
- hash rate, difficulty, block time, reward, DAA, blue score, height
- /api/supply
- circulating by the emission rule, the cap, the halving table
- /api/explorer
- ?blocks=N, ?block=hash, ?height=N, ?tx=hash, ?txs=N, ?address=addr, ?proving=1, ?stats=1, ?dag=N, ?search=q
- /api/checkpoint
- the newest certified checkpoint with its voter table and headers; ?index=N for one
- /api/live
- the observer's feed: blocks of the last 90 s, miners, events, finality, proving
Every answer names the network (the Igneum 2.0 devnet) and the chain id the node reports (4465). The RPC itself is at rpc.devnet.igneum.network (read methods and eth_sendRawTransaction, 20 requests per second per address).
Four words, used exactly. Included: the block carries the transaction. Executed: the EVM ran it and the result is on the record. Proven: a valid proof record for its block was carried and paid. Finalised: the block sits under a certified checkpoint, two thirds of active and of total weight. A pause in finality is shown as a pause, never as a block losing its lock. The definitions are the finality specification’s: section 9, the guarantees.