Exporting Tokens and Transactions

sigma

TL;DR

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

Export tokens or transactions

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

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.

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

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

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

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.

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

A word on rounding

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

    • 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"

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

fire

Last updated