> For the complete documentation index, see [llms.txt](https://docs.vechain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vechain.org/core-concepts/wallets/veworld/user-guide/activities.md).

# Activities

{% tabs %}
{% tab title="Mobile" %}
To see your history you should:

1. Go to your Dashboard
2. Tap the History button
3. You'll see a list of activies (some of them are onchain, some aren't)
4. Tap one of them to read more
5. In each details you'll see:
   * From and To Address
   * Datetime of creation
   * Value (which and how many tokens)
   * Transaction ID (you can also copy it in your clipboard)
   * Blocknumber
   * Network
   * Button to read details of that transaction in the Blockexplorer
     {% endtab %}

{% tab title="Browser Extension" %}
To see your history you should:

1. Go to your Dashboard
2. Click the History button
3. You'll see a list of activies (some of them are onchain, some aren't)
4. Click one of them to read more
5. In each details you'll see:
   * Activity type
   * Status
   * Transaction ID (you can also copy it in your clipboard)
   * Network
   * Finality
   * Datetime of creation
   * From and To Address
   * Value (which and how many tokens)
   * Button to read details of that transaction in the Blockexplorer
     {% endtab %}
     {% endtabs %}


---

# 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.vechain.org/core-concepts/wallets/veworld/user-guide/activities.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.