> For the complete documentation index, see [llms.txt](https://docs.oisy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oisy.com/using-oisy-wallet/how-tos/exporting-tokens-and-transactions.md).

# Exporting Tokens and Transactions

{% hint style="info" icon="sigma" %}
**TL;DR**

OISY allows you to export your token or transaction lists into a text file in CSV format.
{% endhint %}

## Export tokens or transactions

{% hint style="danger" icon="triangle-exclamation" %}
Please have a look at the [chapter on rounding](#a-word-on-rounding) before you process the exported data via a spreadsheet tool.
{% endhint %}

You can initiate your export on the "Settings" page:

<figure><img src="/files/8fIAzmJfiVbAB1Cv3ngy" alt=""><figcaption></figcaption></figure>

The **Basic** exports contain a smaller set of exported columns and focus mainly on the information needed to get a good overview and don't expose blockchain specific details.

**Extended** exports also add blockchain specific information to the exports, such as contract addresses, token precision, or token standard. Those are intended for advanced crypto users.

Please verify that all token balances and prices have completely loaded before you start an export, or you might miss some some tokens or transactions in the export.

{% hint style="info" %}
You can access the Google Sheets template we made for the following screenshots and make a copy for your own use.\
<https://docs.google.com/spreadsheets/d/1RWnR_Y0qqMQmHuWjSko7oWEfzuhcXGqIcmusEt3omv0/edit?usp=sharing>
{% endhint %}

### Token Exports

**Basic**

* Exports a minimal set of columns
* The **Balance** is exported regular number, e.g. 12.4789654
* The **Value** is exported in your currently selected currency

<figure><img src="/files/45rKvqX3gOLP5VHuMXle" alt=""><figcaption></figcaption></figure>

**Extended**

* Also exports the token standard and the address of the token
* The **Balance** is exported as full integer, together with the number of digits precision
* **Price** and  **Value** are both exported in USD and in your currently selected currency

<figure><img src="/files/oVQURQUJEk7uQqLsa6jL" alt=""><figcaption></figcaption></figure>

### Transaction Exports

**Basic**

* Exports the core data for a transaction
* The **Timestamp** is in your local timezone
* The **Amount** is exported regular number, e.g. 12.4789654
* The **Counterparty** shows either the sender address (for a receive) or the destination address.\
  It's resolved into the contact name (and address alias in parenthesis) if found.
* The **Fee** is shown separately.
* To help summarizing, 3 additional helper columns show the amount either as **Credit** (for incoming) or as **Debit**. The third column, **Fee Token Debit**, shows the fee amount paid with the network native coin on EVM networks (mostly ETH).
* It also shows the **Transaction ID**.

<figure><img src="/files/ZE5sgqPQrqYXnWt3MKtr" alt=""><figcaption></figcaption></figure>

**Extended**

* Shows some additional columns compared with the Basic version
* **Timestamp** is in UTC (Zulu time, GMT, ...)
* Also shows **From** and **To** addresses for all transactions
* And also contains an **Explorer Link** to an app showing this specific transaction

<figure><img src="/files/8rLRrjMRZXOuzH2gF74V" alt=""><figcaption></figcaption></figure>

## A word on rounding

{% hint style="success" %}
Crypto tokens often use a precision of 18 or even up to 24 digits after the decimal separator, which can lead to numbers that need a larger amount of digits to represent.\
Spreadsheet tools usually only allow up to 15 significant digits per numeric value, which can lead to a loss of precision when importing them, or that a value is then imported as text instead of a numeric value.

**Note that OISY exports the full precision into the CSV text files. Rounding can happen when importing them into spreadsheet tools.**
{% endhint %}

### Problems

**Problem 1 - Precision**

* Tokens use up to 24 places after the decimal point to store a balance. For example you can have `1234.123456789012345678901234 NEAR`, a number that needs 28 digits to represent.
* Spreadsheet tools can only store at max 15 significant digits (leading and trailing zeros don't count) per numeric value, for example:
  * `1234567890123450000000000` (stored as `123456789012345e10)`
  * `1234.12345678901`
  * `0.123456789012345`&#x20;
  * `0.00000123456789012345` (stored as `1.23456789012345e-6)`

**Problem 2 - Automatic conversion with precision loss**

When you import a text file into a spreadsheet tool, a value that represents a numeric value can automatically be converted into a number and then cut to the maximum precision, so

* The value in the CSV fils is `0.1234567890123456789`
* The resulting value in the spreadsheet will be `0.123456789012345`

Note that spreadsheet tool allow to import without automatically converting a cell into a numeric value. In this case the value would be imported as a text:

* `"0.1234567890123456789"`&#x20;

But this cell then can not be used in mathematical functions.

{% hint style="danger" icon="fire" %}
This means that it's not always possible to import all balances and amounts as numbers into a spreadsheet while keeping the full precision.\
But having 15 significant digits mean that if some digits are cut off, they contribute less than 0.0000000000001% of its value, so the rounding is not all too bad.
{% endhint %}

{% hint style="success" %}

1. OISY exports all token amounts with full precision into the CSV export files.
2. The **Basic** exports export them as regular numbers, containing a decimal point.
   * `5.1234` USDC will be exported as `5.1234`
3. The **Extended** exports write the amounts as Integer value without decimal points, and also exports a column indicating the number of digits precision of the token.
   * `5.1234` USDC will be exported as `5123400` and a column indicating that USDC has `6` digits precision

The Basic exports allow to easily import the numbers anywhere without further processing, but you might lose those digits after 15.\
While the Extended exports allow safer imports, as large integer value are usually not automatically rounded by spreadsheet tools, and remain a text value.
{% endhint %}


---

# 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.oisy.com/using-oisy-wallet/how-tos/exporting-tokens-and-transactions.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.