> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/truvera-workspace/transaction-history.md).

# Transaction history

To see a historical list of your used API transactions and issued credentials, click on the Activity menu item. This page shows a historical list of credential issuance events and blockchain transactions, such as DIDs and revocation.

In the line chart you will see your live transaction history (test mode is not counted).

<figure><img src="https://downloads.intercomcdn.com/i/o/797839765/6053c2b5a3398184cb3f9dd8/Screenshot+2023-08-01+at+17.30.59.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To protect user data, issued credentials never go on the blockchain.
{% endhint %}

You can view the transactions on the blockchain by clicking on the status icon on the right of the transaction that links to the [blockchain viewer.](https://dock.subscan.io/)

<figure><img src="https://downloads.intercomcdn.com/i/o/797839983/666d43435647e376adf1f061/Screenshot+2023-08-01+at+17.31.13.png" alt=""><figcaption></figcaption></figure>


---

# 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://docs.truvera.io/truvera-workspace/transaction-history.md?ask=<question>&goal=<endgoal>
```

`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.
