Activity
Use Activity to inspect indexed events for your account and trace each one to its blockchain transaction.
Activity is the indexed event history for your own account on the active network. A blockchain event is a record of something a transaction actually did on chain, and Activity shows only events the Console has already processed and made searchable, never work that is still in flight. Use it after an operation to confirm what happened, not to decide whether pending work still needs your approval; that question belongs on "Actions".
Activity's scope follows two things at once: your signed-in account, and whichever participant the header currently shows you Acting asDelegated Authority lets a signed-in operator work inside another party's account. One check decides who may enter; the party's own roles decide the rest.Read the concept. Switch participant or switch network and the events you see change to match, the same way Portfolio and Invest change. This differs from Search, where asset visibility follows only your own signed-in account regardless of who you are acting as. A reader who assumes Search narrows the same way sees fewer assets there than Activity shows for the same participant.
Select the network you want to investigate in the sidebar. Reading Activity changes no on-chain state or pending operation. Switching participant or organisation clears cached queries and returns you to the dashboard, so select the participant before you set filters.
A submitted operation lives in the tray for six live phases, in order: preparing, awaiting approval, signing, submitting, confirming, and indexing, before it settles as complete. Undo stays available through preparing, awaiting approval, and signing; once submitting starts, Undo is no longer available. Still processing and failed are off-track outcomes that can end the sequence early, from any of those live phases, not only from one point in it.
On-chain confirmation and indexing are separate steps. The tray shows Indexing while the platform waits for the indexer to process the transaction. Activity lists indexed events; it does not list pending submissions.
Open Activity
Select "Activity" in the Console sidebar. Rows load newest first, sorted by the time the blockchain recorded the event.
Activity lists indexed events for your account on the active participant and network, with the ledger references needed to trace each one.
Find the event
Sort by "Event", "Block", or "Time", and filter by event type. The other columns do not support filtering. To find a time window, sort by "Time" and move through the pages; Activity has no full-text search or date-range picker.
"Export" saves the current page of rows as CSV or JSON. "View" lets you hide columns without changing which events load.
Inspect event details
Select a row to open its detail sheet. "Event Information" shows the category, sender, timestamp, transaction reference, emitter, and block number. "Gas Fee" appears when the event carries gas data. A missing fee means the event has no recorded gas data.
"Event Data" lists decoded event arguments when available. "Involved Addresses" lists other addresses named in the transaction.
For an ERC-4337 UserOperation, the sheet also shows "User Operation", "Sponsored by", and "Sponsored amount". An ERC-2771 forwarder does not use these rows. For relayed transactions, "Sender" identifies the account that authorized the operation, "On-chain sender" identifies the submitting address, and "Meta-transaction signer" identifies the signer when that information is available. Check these fields together when tracing a relayed operation.
Use the tray for work still in flight
Activity itself never shows in-flight work; it only shows history. For anything you just submitted, open the Activity tray from the activity icon fixed in the page's top-right corner, which carries a live count badge for whatever is still in flight. The tray stays available on every private page, not only this one, and it tracks the live phase sequence shown above. It gives you an Undo option while an operation is still preparing, awaiting approval, or being signed; once it starts submitting, that option is gone for good.
Troubleshooting
The event is not present yet
Signal: you know a transaction went through, but no matching row appears. Cause: Activity shows only fully indexed events, and indexing is the last of six phases a submission passes through. A transaction that confirmed on chain moments ago can still be sitting in Indexing rather than Complete. Fix: open the Activity tray to see the live phase, and reload the Activity page once the tray shows Complete rather than assuming Confirming or Indexing means the row already exists here.
The tray shows Indexing for longer than expected
Signal: an operation reads as complete elsewhere but the tray has not moved past Indexing. Cause: a raw Completed state on chain is intentionally mapped to Indexing rather than Complete, because Complete requires the indexer's own projection to confirm the event separately from the chain's own confirmation. This is expected behavior, not a stuck state, for the short window between on-chain confirmation and indexing. Fix: wait for Complete rather than treating on-chain confirmation alone as proof the row will already be here. If the tray sits in Indexing well past the usual delay, treat it the same as any stalled entry, and select Retry if the tray offers it.
The sender shown is a relayer
Signal: the Sender column names an address you do not recognize as the account you expected. Cause: the event went through an account-abstraction bundler or a meta-transaction forwarder, so the on-chain sender differs from the account that actually authorized the operation. Fix: open the event detail. It separates Sender, meaning the authorizing account, from On-chain sender and, when present, Meta-transaction signer, so you can confirm who really authorized the operation rather than reading the raw transaction sender as the answer.
Activity cannot load
Signal: the table area shows a generic component error instead of your events. Cause: a query failure at the table level, most often tied to the active participant or network. Activity carries no dedicated error message for this; the fallback you see is the same generic loading-failure notice other tables in the Console show, not custom Activity copy. Fix: confirm the active participant and network, then retry. A participant or organisation switch clears every cached query and returns you to the dashboard, discarding whatever Activity view you had open, so reload the page fresh after switching rather than expecting your filters to survive it.