> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/operation-history.md). # Reviewing operation history How to read, filter, and interpret an Account's operation history on Ledger Enterprise. **Role: Operators and Administrators.** An Account's **Transactions** tab is its full activity record: transfers in and out, staking activity, message signatures, and token movements. ## Reading the list Each operation shows its type, its counterparty, its on-chain hash, when it was created, the amount, and its status. The header shows how many operations match your current filters, so you can tell whether a filter is hiding something. Per operation you can open its details, view it on a public block explorer, or mark it as spam. ## Sorting and filtering Sort by date, amount, or status. Filter by operation type, date range, amount range, status, and whether an operation is marked as spam. Clear filters individually or all at once. Filters live in the page address, so a filtered view can be shared with a colleague or kept as an audit reference. ### Spam Zero-amount incoming transfers are hidden automatically. Pushing unsolicited entries into an address's public history is a common nuisance, and it is noise rather than activity. Use the spam filter to show them, and mark or unmark individual operations yourself. ## Operation details Opening an operation adds: * The amount in the asset's units and in countervalue * The Account, and the counterparty address * The hash, and the status with its explanation * The fee actually paid, the strategy chosen, and the fee breakdown * The approval history, where the operation came from a Request From here you can view it on a block explorer, copy a link to it, or change its spam marking. ## Confirmations A confirmed operation shows how many network validations it has accumulated. What counts as settled is a per-network judgment, so use the validation count rather than the label alone when the amount matters. ## When an operation fails Failures name their reason. The distinction that matters most is **whether the funds moved**: a rejected Request, or a transaction that never broadcast, leaves your balance untouched. The full list of reasons and what to do about each is in [**Statuses and errors**](/help-center-v2/reference/statuses-and-errors.md). The operation details give the explanation and, where it makes sense, a shortcut back into the send form with the original details pre-filled. > **Important:** A pending Request is not a pending transaction. A Request that has not reached its approval quorum has not touched the chain: see [**How governance works**](/help-center-v2/concepts/how-governance-works.md). ## Exporting Workspace-level exports come from **Reports**, not from an individual Account. See [**Reports**](/help-center-v2/guides/reporting.md). ## Related * [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.md) * [**Statuses and errors**](/help-center-v2/reference/statuses-and-errors.md) * [**Finding Accounts and balances**](/help-center-v2/guides/accounts/finding-accounts-and-balances.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.enterprise.ledger.com/help-center-v2/guides/transactions/operation-history.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.