Activity is the indexed event history of one participant's wallets on the active network. A blockchain event is a record of something a transaction did on chain, and Activity shows only events the indexer has already processed and made searchable, never work that is still in flight, which Submissions shows. Use it after an operation to confirm what happened. Whether pending work still needs your approval is answered on Actions. A second tab, Confirmations, lists the transaction confirmations the platform issues for token movements on your wallets.
The list covers the wallets of one participant: your own, or the participant you work as through “Working as”. It reads one organisation and the active network, so a switch of participant or network changes the events you see, the same way it changes Portfolio. Every signed-in, onboarded user sees Activity in the sidebar, with no role needed. Reading Activity changes no on-chain state and no pending operation.
The “Events” tab shows the time range control, the “Events over time” chart and a table of indexed events for your wallets on the active network.
Each row shows the time, the event with its source and destination, the transaction and the amount.
Steps
Open Activity
Select Activity in the Console sidebar. The page has two tabs, “Events” and “Confirmations”, and the line under the title reads “For”, then your wallets, then “on” and the active network. When more than one wallet is in that line, each shows its short address under its name, so two wallets with the same participant name read apart.
The time range control over the table offers “24 hours”, “7 days”, “30 days” and “All”. It opens on 30 days, and the page address keeps your choice as ?range=. The “Events over time” chart over the table counts the events of that range per hour for 24 hours and per day for 7 and 30 days. When the chart counts per day over 60 days or more, as “All” can, it turns into a calendar of days shaded by how busy each day was. The chart counts the same events as the table, so its buckets add up to the table total. Drag across the strip under the chart to show only the events of that stretch of time in the table, and select Clear selection to return to the whole range. The strip does not work from the keyboard, so use the table's filters and time sort to reach the same events. On a narrow screen, such as a phone, the page leaves the chart out so the first rows fit on the first screen.
Find the event
The table lists the events of the chosen range, newest first, 20 to a page. Search, sort, filters and paging run on the server, so the table reaches every event in the range, and the page address keeps them so a link or a reload restores the same view.
- Search activity matches the event name, the asset name, symbol and address, the transaction hash, and the contract, sender, account, relayer, meta-transaction signer and paymaster addresses. A full address also finds every event that involves it. Search does not read the event's decoded values.
- Sort by “Time” or “Event”.
- Filter by Event, which can also exclude an event type, and by “Asset”. The “Network” filter appears when your scope spans more than one network. Each “Asset” and “Network” option shows how many events it matches.
- The table shows “Time”, “Event”, “Transaction” and “Amount”. View adds “Asset”, “Block” and, when more than one network serves your scope, “Network”. The amount carries a plus or minus sign from your side of the movement.
Each row names a source and a destination. A transfer goes from its sender to its recipient. A mint starts at “System” and a burn ends at “Zero address”. A role grant or revoke ends at the account that gains or loses the role. An event with no named recipient ends at the contract that emitted it.
A mint, burn or transfer of a DALP asset shows as one row. The asset also emits the standard ERC-20 Transfer event for the same movement, from or to the zero address for a mint or burn. Activity does not list that Transfer a second time, and the total, the pager and the Event filter counts leave it out. A plain ERC-20 token emits only Transfer, so its transfers still show. An operation sent through a smart wallet names its contract “Smart wallet entry point”. A smart wallet itself shows its address.
When a new block adds events that match your view, a button such as “3 new events” appears over the table. The rows do not move until you select it, and selecting it returns you to the first page.
For a very long history, counting the events can take longer than the 25 seconds Activity allows. The table then still lists the events and pages through them, and the “Events over time” chart still draws the range with its own count. The pager shows only the current page number, the “Event”, “Asset” and “Network” filters offer no options, and the new events button does not appear. Choose a shorter time range or search for something narrower so the count fits within that limit.
Export saves every event that matches the current filters as CSV or JSON, not only the page on screen. It reads the full set page by page and shows its progress, for example “Loaded 40 of 120 rows…”, while it runs.
Inspect event details
Select a row, or View details in its row menu, to open the event. The row menu also offers “Copy transaction hash”, “View on explorer” and, for a mint, burn or transfer whose transaction is final, “Download confirmation (CSV)”.
The event opens with its name in your Console language, its category and the date in UTC, then the source, destination and amount. The details then show:
- Contract names the contract that emitted the event.
- Initiated by names the account that authorised the operation, marked “You” when it is yours.
- Transaction carries “Copy transaction hash” and “View on explorer”, followed by “Block” and “Network”.
- Event data lists the event's decoded values with readable labels: a date value reads as a date and time, a list or record reads as numbered rows with each address named, and each flow of an XvP settlement reads as Asset, From, To and Amount rows.
- Involved addresses lists the other accounts the event touches.
- Technical holds the raw hashes, the encoded values and the transaction index.
The page address keeps the open event as ?event=, so a reload or a copied link reopens it, even when the event is no longer on the loaded page. A link to an event that does not exist on your wallets shows “Event not found”.
A trade that a trading venue settled shows as one row that reads, for example, “Swap: 10 EQ for 1,000 USD”, with “10 EQ” as its amount. Its event details name the seller and the buyer, Sold for the asset delivered, and “Paid” for what the buyer spent: the quote amount plus the buyer fee, so a 1,000 USD trade with a 1.50 USD buyer fee reads “Paid 1,001.5 USD”. The transfers that settled it fold under the swap. Each transfer names who sent and who received it. A party your role may not see reads “Counterparty”.
For a relayed or sponsored operation, a Relayed section names the “Relayer type”. An ERC-4337 UserOperation shows “User Operation”, “On-chain sender”, “Sponsored by” and “Sponsored amount” when they are known. An ERC-2771 forwarder shows “Relayer”, “Meta-transaction signer” and “On-chain sender”. Read these with “Initiated by” to see who authorised the operation and who submitted it.
Download a transaction confirmation
A transaction confirmation is the record the platform issues for each token movement on your wallets once its block is final, meaning the chain can no longer undo it. Open the Confirmations tab of Activity to list them, newest first. The tab loads 50 at a time, and “Load more” reads the next 50. Each row shows “Time”, “Movement”, “Asset”, “Amount”, “Wallet”, “Counterparty” and “Transaction”, and “View” adds “Block”.
The “Confirmations” tab shows the confirmations the platform issued for token movements on your wallets, with the “Search by transaction hash” field and the “Export” button above the table.
- To find one confirmation, type the full transaction hash in Search by transaction hash. A partial hash shows “Enter the full 66-character transaction hash, starting with 0x.” The page address keeps the hash as
?search=. - Open the row menu and select Download confirmation (CSV) or “Download confirmation (XLSX)”. The menu also offers “Copy transaction hash” and “View on explorer”.
- To save the list itself, use Export, which saves every confirmation that matches as CSV or JSON.
You can also download a confirmation from an event. The event details of a mint, burn or transfer show a “Confirmation” section and a Download confirmation button. Until the transaction is final, the section reads “No confirmation yet. It is available once the transaction is final.” and the download gives the same message. When the tab reads “No confirmations yet”, no token movement on your wallets is final yet.
Activity for a participant or an entity
An operator reads the same kind of event history for someone else from that record's own page. The activity log of a user participant opens from the user's page under Users, and the activity log of an entity from the entity's page under Entities. A participant's log lists the indexed events of that participant's wallets. An entity's log lists the indexed events that involve the entity's account address. A record you are not allowed to read returns no rows and no error, so an empty log can also mean you may not read that record.
You can read an entity's log when its address is one of your wallets, a smart wallet that you control, or a data feed registered to the system. The Identity manager and Verification issuer roles also reach the organisation's wallets and registered identity addresses, and the Permission manager, System manager, Auditor and Gas manager roles also reach the system's paymaster and the organisation's bundler wallet.
On those pages, the Activity log tile counts the record's events over a range you pick: the last 24 hours, the last 7 days or the last month. It opens on 24 hours. It draws the count as a small chart, states it as, for example, “12 events in the last 24 hours”, lists the two most recent events under “Most recent”, and links to the full list with “View full activity”. The range ends at the time of the network's latest block.
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 phase a submission passes through before the tray reports Complete. A transaction that confirmed on chain moments ago can still be sitting in Indexing rather than Complete. Fix: open the Submissions 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 account that authorised an operation is not the account that submitted it
Signal: “On-chain sender” names an address you do not recognise. Cause: the operation went through an ERC-4337 bundler or an ERC-2771 forwarder, so the account that submitted the transaction is not the account that authorised it. Fix: read Initiated by for the account that authorised the operation, and the “Relayed” section for the relayer, the sponsor and, when known, the meta-transaction signer.
Activity shows no events
Signal: the Events tab reads “No events on your wallets yet” or, for a shorter range, “No events in the last 30 days”. Cause: your wallets have no indexed events in the chosen range on the active network. Fix: select the button under the message, such as Show all events, to widen the range. When your identity is not registered, “No events on your wallets yet” also links to “Register your identity”. When the tab reads “No network serves this scope” and “Pick a network under Network in the user menu.”, open the account menu at the top right, point at “Network” and pick a network there. When the tab reads “No network is active”, the organisation has no active network. An organisation owner or platform administrator selects “Open Networks” to add one on Networks, or to retry a network that failed to deploy. Anyone else reads “Ask an organisation owner to add a network.”
Activity cannot load
Signal: the events area shows the Console's general loading error instead of your events. Cause: the events read failed. Fix: confirm the participant in Working as and the active network, then reload the page.
API routes
The Platform API serves the same reads, from indexed data only:
GET /api/lists your events with the filters, search, sort and cursor paging the Console uses. The first page carries the total and the counts per Event, Asset and Network option. When counting takes longer than 25 seconds, the first page still returns its rows andv2/ users/ me/ events meta.nextCursor, leaves outmeta.totalandmeta.facets, and setsmeta.totalsSkippedtotimeout. A missing total then means it was not counted, not that it is zero. A retry counts again and often runs out of time again, so narrow the time range or search to get the counts. Passcounts=falsewhen you only need the rows. A page withoutmeta.totalleaveslinks.lastout, because the last page is not known.GET /api/counts your events per bucket over a window, for the same wallets and filters, so its total equals the list total.v2/ users/ me/ activity- metrics GET /api/andv2/ participants/ {participant Id}/ activities GET /api/read a participant's events and their counts. A participant you cannot read returns an empty page.v2/ participants/ {participant Id}/ activity- metrics GET /api/andv2/ system/ accounts/ {account Address}/ activities GET /api/read one account's events and their counts, under the same access check.v2/ system/ accounts/ {account Address}/ activity- metrics GET /api/lists confirmations and filters byv2/ reporting/ confirmations transactionHash.