Documentation

What this explorer is

Nura Explorer follows an EVM node block by block, writes what it reads into an index of its own, and serves that index back as pages you can link to. Nothing on the site is an estimate: every figure is counted from blocks the chain has already sealed.

It asks for no account and keeps none. There is nothing to sign up for, nothing to install, and no wallet has to be connected to read any page here.

Finding something

One field in the header takes all three identifiers - an account address, a transaction hash, or a block number. It works out which one was pasted and opens the page for it, so there is nothing to choose first.

A value that finds nothing is usually one of two things: a character lost from a hash, or a block the indexer has not reached yet. The home page says how far behind the node the index is, so a transaction from moments ago is worth asking for again shortly.

The sections

Five sections, each answering one question about the chain.

Blocks

Every block in order, newest first, with its height, its age, the transactions it carried and the gas they spent.

Transactions

Every transaction the index holds, and a page for each one: sender, recipient, value, fee, status, and the transfers the call actually made.

Accounts

Accounts ranked by native balance. These are read live from the node rather than from the index, because a stale balance is a wrong one.

Governance

The chain’s proposals - what each would do, where its vote stands, who has voted, and what it still needs to pass.

Charts

The index added up over time: transactions, blocks, addresses, fees, gas and contract activity, across a week, a month or a quarter.

Reading chain data

Address

An account: twenty bytes, written as forty hexadecimal characters after 0x. The same shape serves a person’s wallet and a deployed contract, and the address page says which of the two it found.

Transaction hash

A transaction’s identity: thirty-two bytes, fixed at the moment it is signed. It names the same transaction in every wallet and on every explorer, which is why it is the thing to quote when reporting one.

Block

A batch of transactions the chain agreed on at one height. Heights count from zero and never repeat, so a block number is an exact point in the chain’s history rather than a position in a list.

Gas and the base fee

Gas measures the work a transaction asks the network to do; the base fee is what one unit of that work costs in the block that included it. The fee charged is the gas used multiplied by the price paid per unit.

Nonce

A counter held per account, one higher on each transaction it sends. It fixes the order they execute in, and it is what stops a signed transaction being replayed a second time.

Transfer

A movement of value inside a transaction, recovered from the logs it emitted - ERC-20, ERC-721 and ERC-1155 alike. One call can produce several, so a transaction lists them rather than reporting a single number.

Decimals

Chain amounts are whole numbers of the smallest unit, and a coin’s decimals say where the point belongs. Every amount here is scaled in exact integers rather than in floating point, so a balance is never rounded into a different number.

Connecting a wallet

Reading needs no wallet. One is asked for only where a page can send something - voting on a proposal, adding to its deposit, or calling a contract that writes - and even then the transaction is built here and signed there, in the wallet, where it can be read before it goes.

Wallets announce themselves to the page rather than being hardcoded, so whichever ones are installed appear in the picker and none of them is favoured. This explorer never asks for a seed phrase or a private key, and no page on it has any use for one.

How governance is read

This is a Cosmos chain with an EVM module, so its proposals live in the chain’s own governance module and never appear as EVM events. They are read from the node’s own interfaces at the moment you ask for them, and nothing is copied into the index - a chain has tens of proposals where it has millions of transactions, so a copy would only be one that can go stale.

Following a proposal and acting on one are separate capabilities. The page shows a proposal wherever the node answers; it offers a vote only where the chain has enabled the precompile that a vote is sent to. A chain with one and not the other is the ordinary case, and the page says which it has.

The API

Every page here is drawn from a public HTTP API under /api, and it is the same one the pages themselves call - there is no private endpoint behind them. Responses are JSON, and the server publishes a machine-readable list of its routes at /api/_manifest.

There is also a small Etherscan-compatible surface, so a wallet configured with this explorer as its API can resolve balances and transaction lists. Both are rate limited per address, so a script that walks the chain should page through results rather than ask for all of them at once.

What this explorer does not do

It counts what the chain has already committed, and nothing else. There is no view of the mempool, so a transaction that has not been included yet cannot be found here, and no pending list exists to look in.

It runs no contract verification service and no market of its own either. A contract’s interface is recovered from its bytecode, so a function whose signature has been published is named while one that has not is printed as the four bytes it is; a price is quoted only where a deployment has configured an exchange to ask, and where none has, the page prints nothing rather than a number nobody measured.

Common questions