Use the Network

Block Explorer

testnet.asentum.com · Estimated read time: 5 minutes

TL;DR

The block explorer at testnet.asentum.com is first-party, served by the same binary that runs the chain. Search accepts block numbers, transaction hashes, and addresses. Contract pages show the full source, not bytecode. Every page is deep-linkable and content-negotiated — the same URL returns HTML to browsers and JSON to tools.

Search

The topbar search bar accepts three kinds of input and routes accordingly:

Block number (bare digits, optional # prefix) → /block/N
Transaction hash (64 hex, 0x-prefixed) → /tx/<hash>
Address (40 hex, 0x-prefixed) → /address/<addr>

Block pages

/block/N shows the height, hash, parent hash, state root, proposer, validator signatures, gas used, base fee, and the transaction list. Click any transaction to drill into its receipt.

Transaction pages

/tx/<hash> shows:

Status (success / reverted), block number, timestamp.
From / To (or deployed contract for a deploy tx).
Value transferred, gas used, tx fee paid.
Method name and decoded arguments (for contract calls).
Events emitted, with args.

Deploy transactions show the deployed address as a gold link that routes straight to the new contract page.

Address pages

/address/<addr> shows balance, nonce, account type (EOA or Contract), and recent transactions. See Account Model for what those fields mean.

Contract pages

Contract addresses get a richer page. In addition to balance + activity, you see:

The full JavaScript source, syntax-highlighted.
A Read section — view methods you can call for free from the UI.
A Write section — send methods that prompt your connected wallet.
The deploy transaction and deployer address.

No Etherscan "verify your contract" step — source is on-chain by construction.

Validators

A panel on the homepage lists the active + pending validator set, their addresses, bonded stake, and status (active, pending, tombstoned). For the protocol context see Consensus & Validators.

Verifying a contract

Verification is a single BLAKE3 hash compare — no multi-step submission, no compiler matching. See Verifying Contracts for the full story.