Verify any number on the explorer

Every live number on this site is read straight from the Anubis chain, but you do not have to take our word for it: each one can be checked on the public block explorer. This guide shows you how.

The official block explorer for Anubis is Anubis Explorer, built on the open-source Blockscout. The search box at the top accepts an address, a transaction hash, a block number or a token name.

Start from "Verifiable on-chain"

Under every live number on this site there is a line of small print such as "● Verifiable on-chain · 1 minute ago". A green dot means the read succeeded, yellow means it has not refreshed for a while, and red means this read failed. Tap the line and it opens up:

• "Direct chain read" or "Indexer": whether the number was read straight from the blockchain, or from this site's indexer, which aggregates on-chain events.
• Contract names with short addresses: each opens that contract's address page on the explorer.
• "Block #number": the block the values were read at; it opens that block's page. The site reads a group of related numbers at one and the same block so they are consistent with each other.
• "Updated …": how long ago the site read the data, for example "Updated 2 minutes ago".

So checking starts with two taps: open "Verifiable on-chain", then follow a link inside it to the matching explorer page. The explorer shows the latest state by default, so if new blocks have been produced in the meantime, the numbers may have moved on. That is expected.

Address pages

Address pages look like https://browser.anubispace.org/address/0x…. The header tells you whether the address is a regular wallet (EOA) or a contract.

Under Details you find:

• Balance: the native coin balance. The native coin of Anubis is DAI, and it also pays the fees (if you added the network with the official dApp's configuration, your wallet shows it as ETH; it is the same balance, see Set up a wallet).
• Tokens: the tokens this address holds and their estimated value.
• Transactions / Transfers: the number of transactions and token transfers.

The tabs below:

Contract addresses also get a Contract tab and a Logs (event log) tab.

Transaction pages

Transaction pages look like https://browser.anubispace.org/tx/0x…. The lines that matter:

• Status and method: Success or Failed. A failed transaction has no effect, but the fee is still charged. Next to it is the method called, for example subscribe.
• Block: the block the transaction is in.
• Timestamp: when it happened, switchable between Local, UTC and Unix. This site shows every time in UTC+8.
• From / Interacted with contract: the sender and the contract called.
• Transaction fee: the fee, also labeled in DAI.

Below, the Token transfers tab lists token movements inside this transaction and the Logs tab lists the events the contracts emitted.

Block pages

Block pages look like https://browser.anubispace.org/block/<number>. They show the block height, time, number of transactions and gas used. Anubis produces a block roughly every second. The block number inside "Verifiable on-chain" on this site is how you pin down exactly when a value was read.

Contract pages: what you can and cannot see

As of 24 September 2026 we checked the main contracts this site reads:

• The Genesis contract 0x030590921E9841e1d2104642ED285C83B5F0ddB5, the community relations contract 0xc9f9a8a2dBf8188AD6610e0239105CAbE67c4993 and the LGNS token 0x4D1D808a081FdAc440703b3765FC61f8028C06B8 are upgradeable proxies (the explorer marks them Proxy, EIP-1967 Transparent Proxy). The explorer shows the source of the proxy itself, but the implementation contract that does the actual work has not been source-verified on the explorer.
• As a result, the Read/Write contract section of their Contract tab lists only the proxy's own fallback and receive. Business views such as stats or getRecords are not available there.
• The DAI token 0x83fd06F0846d9D90B3016bF670Efe2E0B11cDe14 is a verified contract (HyperlaneSyntheticToken).

So to check protocol data you rely on transactions, token transfers and event logs rather than Read contract. The Genesis Plan makes a good example.

Worked example: checking the Genesis Plan

1. Check the total raised

   Open the Genesis contract's address page and look at Balance and Transfers under Details. As of 24 September 2026, Balance shows 14,999,976.57 DAI and Transfers shows 5,949, matching the total raised and the record count on our Genesis Plan page.

2. Check individual records

   Switch to the Token transfers tab. Every successful Genesis contribution appears as a DAI transfer from the participant's address into the contract.

3. Read the event log

   Open any successful subscribe transaction and switch to its Logs tab. You will see two events: a Transfer from the DAI contract and a Subscribed from the Genesis contract.

The real event is Subscribed(recordId, subscriber, daiAmount, timestamp):

Take transaction 0x97962f…83e5:

• Topic 1 is 0x…173c, which is 5948 in decimal: record ID 5948.
• Topic 2 is the address 0x1A39449B796dF8d3c664601360017Ef497224948.
• The first half of Data, 0x…056bc75e2d63100000, equals 100 × 10^18, so 100 DAI; the DAI Transfer in the same transaction is also 100 DAI.
• The second half of Data, 0x…6aae08da, equals 1789790426, which is 2026-09-19 12:00:26 (UTC+8).

Those are exactly the four fields of one row in the "Latest records" table on our Genesis Plan page.

Units

On chain, amounts are whole numbers without a decimal point. Convert them with the token's decimals:

The explorer's token transfer lists convert for you; the raw data in event logs does not.