Skip to main content
Explorer
Aptos Explorer

Account address or name · Txn hash or version · Block height · Coin type · ANS name

User Guide

This guide explains how to use Aptos Explorer, how to read the pages it shows, and how to configure it in your browser. It is written for people looking up on-chain data — not for operating a node or writing Move.

What this explorer is

Aptos Explorer is the official block explorer for the Aptos blockchain. You use it to look up transactions, accounts, blocks, validators, coins, NFTs, and network status. It reads public chain data; it does not take custody of funds and it is not a wallet.

Every page is scoped to a network (mainnet by default). A transaction or account on testnet is a different object from the same identifier on mainnet. The network is stored in the URL as ?network=… so links you copy keep the same chain.

The explorer is a website. Connecting a wallet is optional and only needed for actions such as staking, running a module function, or submitting a Move script.

Finding your way around

The header is on every page: logo (home), main navigation, network selector, optional share button, user guide, settings, light/dark theme, and wallet connect. On smaller screens, navigation, settings, theme, and wallet live in the menu button.

Under the header, most detail pages show a back control (when you have in-app history) and a search field. The home page (/) is a larger search surface with the same matching rules.

The footer has Privacy, Terms, token verification instructions, this guide, and Clear Cache (clears the browser search result cache, not the blockchain).

  • Transactions — recent user transactions, with filters.
  • Analytics — mainnet-only charts (TPS, active users, gas, and more).
  • Validators — the validator set and delegation pools.
  • Blocks — latest blocks by height.
  • Coins — listed coins and fungible assets.
  • Releases — live network versions, AIPs, and SDK/CLI releases.
  • Run Script — advanced tool to simulate and submit a raw Move script.

Networks

Use the network dropdown in the header. In-app links keep your current network so you do not silently jump back to mainnet.

Mainnet is production. Testnet and devnet are for development (devnet is reset often). Local talks to a node on your machine (typically http://127.0.0.1:8080/v1). Hidden or preview networks may appear when the explorer is built with a feature flag.

If you select Local and the node is not running, a modal explains how to start aptos node run-local-testnet and offers a switch back to Mainnet.

Some features are mainnet-only (analytics, some price estimates, Sentio traces). GraphQL/indexer tabs may be missing on networks that do not publish an indexer.

Reading a transaction

Open a transaction at /txn/{version} or /txn/{hash}. Version is the ledger sequence number (an integer from 0). Hash is the 32-byte transaction hash. Version is the stable identifier if you have it.

The transactions list shows recent activity. User vs All chooses user-submitted transactions versus the full stream (including block metadata). You can filter user transactions by entry function (fn_addr, fn_module, fn_name in the URL).

On the detail page, tabs depend on the transaction type:

  • Overview — status, sender, gas, function, and parsed Actions (swaps, transfers, and similar).
  • Payments — shown only when the explorer identifies a payment (peer-to-peer, partner-controlled hops, confidential transfers, wraps/unwraps, or exchange legs). Confidential amounts stay hidden.
  • Balance Change — coin and fungible-asset balance diffs, including gas.
  • Events — logs emitted during execution.
  • Payload — the submitted payload (entry function, script, multisig, and so on).
  • Changes — write-set resource changes.
  • Modules — when the transaction publishes or upgrades Move packages.
  • Trace — experimental Sentio Move call trace on mainnet user transactions.

A failed transaction still exists on-chain; the overview shows the error. Pending transactions have not yet been ordered into a block.

If the serving fullnode has pruned old history, the explorer retries an archive node, then reconstructs from the indexer if needed. Indexer-only pages may omit payload arguments, events, or hashes, and they show an info banner.

Accounts, names, and objects

An account is a 32-byte address. Open it at /account/{address}. Short hex (0x1) is accepted. Aptos Names (.apt) resolve to addresses in search and in the account header.

A Move object is a first-class on-chain entity that can own resources. If you open an object address as an account, the explorer redirects to /object/{address} with a similar tab set.

Account tabs typically include:

  • Transactions — history for this address, with pagination and optional function filter.
  • Coins — coin balances (and related FA views where applicable).
  • Tokens — NFTs and digital assets.
  • Resources — Move resources stored under the account, as JSON.
  • Modules — published packages and source (see Modules).
  • Multisig — when the account is a multisig (Petra Vault onboarding may be offered).
  • Info — sequence number, authentication key, and related metadata.

Known addresses can show a label and icon (exchanges, framework accounts, and so on). Some labeled projects show a defunct or winding-down banner — treat that as a warning, not investment advice.

The balance card shows APT. On mainnet it may include a USD estimate from a public price feed.

Move modules and code

The Modules tab lists packages published by an account or object. You can open packages, code for a module, Run (entry functions, wallet required), and View (read-only view functions).

Code views include Published Source (if the publisher stored it), ABI, and — when you opt in under Settings — Decompiled bytecode and Disassembly. Decompilation runs in your browser (WebAssembly). It is a reconstruction, not the original comments and names.

A version selector lets you inspect a package at an earlier publish transaction. Diff view compares two versions. Cross-module links jump to other modules in the same package when names resolve.

Blocks

Aptos groups transactions into blocks ordered by height. The blocks list shows recent heights. A block page (/block/{height}) has Overview (timestamp, proposer, transaction count, hashes) and Transactions in that block.

Pruned blocks follow the same archive-node fallback as old transactions. The recent-blocks table stays on the serving fullnode window.

Validators and staking

The validators page has All Nodes (the current validator set, voting power, location when known) and Delegation (pools you can stake to). An epoch indicator shows the current epoch.

Open a pool at /validator/{address} for commission, stake, performance, and — if you connect a wallet that has deposits — My Deposits with stake / unstake / restake / withdraw. On a phone, those actions are on each deposit card, not only in the desktop table.

Delegation is a protocol action: it spends gas and uses your wallet. Read amounts and the lockup before confirming.

Coins, fungible assets, and NFTs

Coins are the original Move 0x1::coin types (address::module::Struct). Fungible assets (FA) are the newer object-based standard. APT exists in both views; many newer tokens are FA-only. The coins list mixes listed coins and FAs.

A coin page is /coin/{type} (URL-encoded type). An FA page is /fungible_asset/{metadataAddress}. Tabs commonly include Info, Transactions, and Holders (holders need indexer support).

NFTs and digital assets use /token/{tokenId} with Overview and Activities. Banned or scam collections may be hidden or flagged.

Verification badges (native, Labs verified, community/Panora, recognized, unverified, banned) are explained on the verification page. A badge is not a guarantee of value or safety.

Analytics

Analytics is mainnet only. Other networks show a short message instead of charts. Charts cover daily user transactions, peak TPS, active users, new accounts, deployments, gas, and block gap. You can switch 7-day vs 30-day ranges.

The strip at the top summarizes supply, stake, TPS, and node counts. Data comes from published chain-stats files plus live chain queries — it can lag slightly.

Releases, AIPs, and tools

The releases hub has three tabs: Networks (epoch, height, framework/node versions, feature flags across mainnet, testnet, and devnet), AIPs (Aptos Improvement Proposals from the public AIP repository), and SDKs (CLI, aptos-node, and official SDK releases).

Older URLs /deployments and /aips redirect here.

Run Script (advanced)

Run Script builds, simulates, and executes a compiled Move script transaction from a connected wallet. Scripts have no on-chain ABI, so you must declare argument types yourself. There is no in-browser Move compiler — paste bytecode (hex) from a compiler you trust.

Treat this as irreversible once executed. Always read the simulation (status, gas, events, resource changes) before Execute. Prefer the account Modules Run tab for published entry functions.

Configuration

Open Settings. Preferences are stored in this browser, not on Aptos Labs servers.

  • Language — Browser default or an explicit catalog (English ships today). This controls translated chrome, settings copy, and this guide. On-chain data (addresses, function names, events) stays as the chain stores it.
  • Move bytecode decompilation — off by default. Read the disclaimer before enabling. When off, Decompiled and Disassembly views are hidden.
  • API key overrides — optional per-network geomi.dev keys so your browser is not stuck on the shared anonymous rate limit. Keys are sent as Authorization: Bearer. Geomi AG-* client keys must allow this site’s Origin. Check Remember on this device only on a machine you trust; otherwise keys last for the tab session.
  • Theme — light or dark from the header sun/moon control. Stored in a cookie (color_scheme) and follows the system if you have not chosen.
  • Network — header selector; encoded in ?network= rather than settings.

Save applies API keys and decompilation (and language) together: cached clients are dropped and queries refresh. Restore Defaults clears these explorer preferences in this browser.

If you see HTTP 429, the rate-limit drawer can send you to Settings. A Geomi body of *Per anonymous IP rate limit exceeded* means no key was accepted; *Per application per IP rate limit exceeded* means your key’s quota was hit.

Wallet

Connecting a wallet is optional. Use it to open your account quickly, stake, run entry functions, or submit a script. Petra is listed first among installable wallets.

The wallet’s network must match the explorer network (with a small exception for some local/custom RPC setups). Mismatched networks block submission so you do not sign for the wrong chain.

Token and address verification

The explorer can show verification badges on tokens and some addresses. Community listing goes through the Panora token list. Labs verification is reserved for native assets and selected established tokens.

Step-by-step instructions for project teams are on the Token & Address Verification page. Users should still check the type/metadata address, not only a name or icon.

URLs, sharing, and agents

Prefer path-based tabs, for example /account/0x1/modules rather than a ?tab= query. Copy the address bar to share a view; keep ?network= if you are not on mainnet.

Canonical templates are documented for humans here and for software in `/llms.txt`. In-browser agents may use read-only WebMCP tools (search, open transaction/account/block/coin/releases/guide) when the browser supports them.

When the explorer is installed as a PWA or embedded (for example Petra Vault), a Share control may appear in the header.

Glossary

  • Address — 32-byte account or object identifier, hex with 0x. 0x1 is the Aptos Framework.
  • ANS — Aptos Name Service. A name like alice.apt maps to an address.
  • Block height — index of a block, starting at 0.
  • Event — structured log emitted while a transaction runs.
  • Fungible asset (FA) — object-based fungible token standard (metadata object address).
  • Gas — fee for execution and storage, paid in APT (octas under the hood).
  • Indexer — Aptos Labs GraphQL API used for history, holders, and some tabs. Not every network has one.
  • Module — published Move code. A package groups modules.
  • Object — on-chain entity with its own address that can hold resources.
  • Octa — 10⁻⁸ APT. 1 APT = 100,000,000 octas.
  • Resource — typed Move data stored under an account or object.
  • Sequence number — per-account counter that orders that account’s transactions.
  • Transaction version — global ledger version (integer) assigned when a transaction is ordered.
  • Write-set / changes — state the transaction wrote.

Troubleshooting

  • Empty or spinning pages — check the network selector and whether you are on Local without a node. Try another network or wait out a 429.
  • Transaction not found — confirm version/hash and network. Very old versions may load from archive/indexer with fewer fields.
  • Search missed a pruned hash — hash lookup uses the fullnode then archive (without the explorer API key). Indexer cannot search by hash.
  • Decompiled / Disassembly missing — enable decompilation in Settings and accept the disclaimer.
  • Wrong chain — look at ?network= and the header dropdown.
  • Stale search hits — footer Clear Cache.
  • Analytics missing — switch to mainnet.
  • Wallet will not submit — match wallet network to the explorer; reconnect after switching.