History

Find any settled operation on this account, see how it ended, and open the on-chain evidence.

Where: Account → History

Settled operations, newest first. History is the record of what actually happened: an entry appears only once a transaction has executed or been cancelled on chain.

What is listed

History holds operations that are finished on-chain. An item arrives here when it is executed, cancelled or fails; until then it lives in Approvals. The counter under the filters reads "N records".

Status	Meaning
Executed	The operation completed and its effect (transfer, mint, configuration change) is on-chain.
Cancelled	An approver cancelled the request, or a signed cancellation was submitted. No effect on balances.
Failed	The execution transaction reverted. Gas was spent; the operation did not happen.

Filters and grouping

• Outcome filters: All · Executed · Cancelled · Failed.
• Group by: None, Date, Result, Operation or Requester. Grouping by Requester is a quick way to review one signer's activity; Operation groups all transfers, all role changes and so on.
• Search activity matches operation names, addresses and transaction hashes.

Columns

Column	Meaning
Operation	Action name, requester and when it settled
Change	Decoded effect, for example the amount and asset moved
Status	Executed, Cancelled or Failed

Open a record

Click a row to open the Transaction history detail. It has the same three views as an open request:

• Summary: what happened, who requested, who approved, when.
• Details: raw parameters, function selector, target address, execution path used.
• Activity: the timeline from request to settlement, with the transaction hash of each step and a link to the block explorer.

The transaction hash is the evidence. Anyone can verify it on the explorer without the Platform.

Where the data comes from

History is read from the chain (events and stored transaction records), not from a Bloxchain database. It is therefore complete even if you open the account in a fresh browser, and it does not depend on signing in. Records are read over the Platform's own HTTPS endpoint for the network, not through your wallet's RPC, so a slow endpoint can delay new rows by a few seconds. Use the refresh control if a row you expect is missing.

Related

• Approvals
• Overview
• Supported networks
• Troubleshooting