> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/transaction-history.md). # Transaction History Review every transaction made by a workspace. ## Transaction History Every transaction the workspace has made, and what each one did. ### The table Each row is one transaction: one instruction, however many chains it touched. A cross-chain allocation is one row, not one per chain. Rows carry the type, status, amount, strategy affected, pools affected, counterparties, and time. ### Reading one Selecting a row opens the details panel. **Amount and fee.** What moved and what it cost. The fee expands into network, bridging, and swapping. **Counterparties.** Where capital came from and went, named rather than left as addresses. **Transaction hashes.** Grouped by chain. A transaction spanning three chains has a hash per chain. **Distribution.** Allocations, redemptions, and rebalances show each holding, project, chain, and amount received. ### Exporting **Export .CSV** writes the filtered set. Unsettled rows are excluded. An export records what happened, not what is happening. ### When something is missing Distribution needs the classifier to index the transaction. Older transactions, or transactions awaiting indexing, show totals without a per-holding breakdown. Empty is not broken. If a transaction settled on-chain and the breakdown is absent, the record is incomplete, not the transaction. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.brava.finance/platform/transaction-history.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.