# Operations, history and statuses

Every account keeps a full history of its activity. This page covers how to browse and filter that history, what an individual operation shows, and how to read each status, including what to do when one fails.

## Browsing the operations list

On an account, the operations list shows its activity with, at the top, the number of transactions matching your current filters. Each entry shows the transaction type (send, receive, stake, NFT, message), the counterparty (recipient for a send, sender for a receive), the transaction hash, the date, the amount, and the status. From an entry you can **view its details**, open it in a **block explorer**, or **mark it as spam**.

You can **sort** by date, amount, or status, and **filter** by type, date, amount, status, or spam. Filters can be cleared individually or all at once. An account with no activity shows an empty view.

> **Note:** Spam is hidden automatically. Transactions with a zero amount are treated as spam and hidden from the list by default, so the history stays clean. You can still surface them via the spam filter, and mark or unmark any operation yourself.

## Operation details

Open an operation to see everything about it: the transaction type, the amount (crypto and fiat), the date, the account, the recipient or sender address, the hash, the status with its explanation, and the fee, including the **fee amount**, the **fee strategy** used, and a fee breakdown. Where relevant you'll also see the **request history** behind it. From here you can open it in an explorer, share a link to the transaction, or mark/unmark it as spam.

For a **confirmed** transaction, the status detail includes the number of validations.

## Reading statuses

Most operations move from pending to confirmed without intervention. When something doesn't complete, the status names the reason, and the operation detail explains it more fully and offers a next step, for example a shortcut back into the [Send flow](/helpcenter2/for-operators/sending-assets.md) pre-filled with the original details so you can try again.

The failure reasons you may see:

| Status                  | What it means                                                                                                                                                  |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rejected**            | An approver rejected the request.                                                                                                                              |
| **Failed to broadcast** | An error stopped the transaction from reaching the network.                                                                                                    |
| **Missing funds**       | The available balance was too low.                                                                                                                             |
| **Max fee too low**     | The fee required by the network was higher than the maximum fee allowed for the transaction.                                                                   |
| **On-chain error**      | The blockchain returned an error.                                                                                                                              |
| **RBF failure**         | A fee-replacement attempt didn't add enough additional fee. (See [Bitcoin: Replace by Fee](/helpcenter2/network-specific-guidance/bitcoin-replace-by-fee.md).) |
| **Amount too low**      | The transaction amount was below the allowed minimum.                                                                                                          |
| **Internal error**      | An internal error occurred while processing the request.                                                                                                       |

> **Note:** A failed transaction stays in the history with its reason, so there's always an auditable record of what happened and why.

## Related

* [How requests and approvals work](/helpcenter2/getting-started/how-requests-and-approvals-work.md): the lifecycle behind these statuses.
* [Sending assets](/helpcenter2/for-operators/sending-assets.md): create a send, or retry a failed one.


---

# Agent Instructions: 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:

```
GET https://help.enterprise.ledger.com/helpcenter2/for-operators/operations-history-and-statuses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.