Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Tools

Keystore Explorer

The Altana Keystore Explorer is a public observer for the Keystore, the onchain registry that records which keys are authorized to act on each Altana Smart Agentic Wallet. It decodes the registry into accounts, keys, and state changes, so you can see every key, on every chain, in its current state.

NetworkExplorer
Mainnetexplorer.altana.network
Testnettestnet.altana.network

Both instances carry a link to the other in the header, so you can switch between them without retyping an address.

No account, API key, or wallet connection is needed. Everything it shows is public onchain state that anyone can read independently.

What you can look up

Search. The search box takes a wallet address, a key id, or a public key hash. A public key hash auto-derives the key id, so you can paste what your code has without hashing it yourself.

Account page (/account/<address>). Everything the registry knows about one wallet: active key count, total keys, chains it has touched, and a table of its keys with type, state, chain, nonce, and last update. Below that is the wallet's own event history.

Key page (/key/<keyId>). One key, in plain language. Whether it is active, revoked, or expired, whether it is an admin or a session key, the account that owns it, the chain it lives on, its expiry, and when it was registered.

Live activity. A running feed of Keystore events across all indexed chains, filterable to registrations, revocations, or L2 cache syncs, with the transaction fee and chain for each.

Networks. The source Keystore contracts and the L2 cache, each with its indexed head block and the time of its last event. Mainnet indexes BNB Smart Chain and Ethereum as sources, with Base as the L2 cache. Testnet indexes BNB Smart Chain Testnet and Ethereum Sepolia, with Base Sepolia as the cache. Contract addresses are listed in Networks and addresses.

How to use it well

Confirm a grant landed. After grantSession, open your wallet's account page. The new session key should appear in the keys table with an expiry. If it is not there, the grant did not reach the chain you are looking at.

Confirm a revocation took effect. After revokeSession, the key page flips to revoked. Revocation is monotonic, so a revoked key never comes back. This is the fastest way to prove to yourself, or to someone else, that authority is actually gone.

Tell revoked apart from expired. These fail the same way in your code and mean very different things. Expired means the session simply ran out and can be granted again. Revoked means it was pulled deliberately. The key page names which one it is.

Debug cross-chain authorization. If a key you granted on Ethereum is not being accepted on Base, filter the activity feed to L2 sync events and check the cache in the networks panel. A missing sync means you still need ensureKeyCached.

Share a link as evidence. Account and key pages are plain URLs, so explorer.altana.network/account/<your wallet> is a self-contained, third-party-verifiable record of what your agent was authorized to do and when. That link is the right thing to hand a counterparty, a reviewer, or a hackathon judge who asks to see your onchain activity. It reads from the same public registry they could read themselves, so nothing about it depends on trusting you or Altana.

Where the explorer is not the answer

The explorer is an indexed view built for humans. It is not the authority, and it is not an API.

For anything your code depends on, read the Keystore contract directly. One free isValidKey call answers whether a key is authorized right now, from any RPC, with no indexing lag. See Verify an agent's authority from anywhere.

Where a live node read is unavailable, a key page will say so and fall back to indexed history. Treat that state as informational and confirm with a contract read.

Related