Using the explorer

The Somnia Explorer shows Somnia Accounts at somnia-platform-explorer.vercel.app/smart-accounts. Use its chain selector to switch between Global (mainnet), Global testnet and Tokyo testnet, the networks with an account factory. Every page reads the public index for the selected network, so it can lag the chain by a few blocks; each panel says how fresh it is.

Page	Path	What it shows
Accounts	/smart-accounts	Account counts, the newest accounts, live activity, a lookup and the factory
Address	/smart-accounts/<address>	Whose account an address is on each network, its owners, modules, authorization and history, or the accounts a key controls

Accounts

/smart-accounts opens with three figures for the selected network:

• Accounts: how many the factory has created here, and the total across every network.
• Newest account: when the latest was created, and the owner key it derives from.
• Index: whether the index has caught up with the chain, or how many blocks behind it is.

Below them:

• Whose account is this? Paste any address: an account, an owner key or a session key. It opens that address's page.
• Accounts lists the newest accounts, with the key each derives from, its index under that key, how many of its owners must sign, and when it was created.
• Activity is every account's latest events: creations, executions and failed executions, owner and threshold changes, modules and guards, and funds received. Each says what it did in a line, such as the contract an execution called and the value it sent.
• Factory shows SomniaAccountFactory on this network: its proxy, implementation, admin, the Safe singleton and fallback handler new accounts get, and when it last changed. The admin can upgrade the factory, but accounts it already created are untouched.

The panel beside the code sample shows the same lookup from the SDK, with listAccountsAt and getActivityPage.

Address

/smart-accounts/<address> shows everything the index knows about one address, on every network it covers. The same address can be a deployed account on one network and empty on another, so when it is an account on more than one, buttons switch between them.

For an account:

• Account on a network: the key and index it derives from, how many owners must sign, executions (and how many failed), when it was last active and created, who paid for its creation, its Safe version and its guard, if any.
• Owners: every current owner, and former ones, with when each was added. An owner can itself be an account.
• Modules: any module enabled on the account. An enabled module can move anything in the account with no owner signing, so it is shown as part of who controls it.
• Authorization: for an account created from one signature, what the owner key signed: who else it let in, the threshold, and until when the signature could be used.
• History: the account's events, newest first, with who sent each one and its block.

If the key the address derives from is no longer an owner, a warning says so. The address always derives from that key, but only the owners listed can move anything.

For an owner key or any other address:

• Accounts it controls: every account where it is an owner, on any network.
• Derived from it: every account whose address derives from it, at each index.

To check an address offline, derive it with accountAddress in the SDK. See Find an account.