← Back to Nah Crypto Tax Tracker
Not tax advice. All numbers, tokens and signatures below are EXAMPLE data. This guide covers record-keeping only. How any of this is treated where you live is a question for a tax professional.
You exported your wallet history from Solscan, opened the file, and the time column is a ten-digit number like 1779128572. Here are tested conversion formulas, and what a trade sheet does when the date stays text.
Solscan's export documentation shows two time columns side by side in its example: Block Time, a Unix timestamp in seconds (e.g. 1779128572), and Human Time, an ISO 8601 text in UTC (e.g. 2026-05-18T18:22:52.000Z). The same docs describe the time filters as "Unix timestamp in seconds" (pro-api.solscan.io). The column names in the file you download from the website may differ, so check your own header row.
Solscan also notes that an export returns "the latest 1,000 records only (even within the selected filtered range)", so long histories need several exports by date range (info.solscan.io).
Both columns are in UTC.
Put the Block Time in column A and the Human Time in column B. Each formula below was tested in LibreOffice Calc on the three EXAMPLE rows in the table further down. The functions used (INT, DATE, VALUE, LEFT, MID) are standard in both programs, and Microsoft documents DATE as returning "the sequential serial number that represents a particular date" (support.microsoft.com). We did not test them in Excel itself.
From Block Time, date only (UTC):
=INT(A2/86400)+DATE(1970,1,1)
From Block Time, date and time (UTC):
=A2/86400+DATE(1970,1,1)
From Human Time text, date only (UTC):
=DATE(VALUE(LEFT(B2,4)),VALUE(MID(B2,6,2)),VALUE(MID(B2,9,2)))
That last one reads the year, month and day out of the text by position, so it doesn't depend on your system's date settings. Microsoft notes that with DATEVALUE "your computer's system date setting may cause the results ... to vary" (support.microsoft.com).
Format the result cells as dates (YYYY-MM-DD). In some language settings, Calc and Excel use a semicolon instead of a comma between arguments.
Google documents a dedicated function, EPOCHTODATE(timestamp, [unit]), where unit 1 means seconds, 2 milliseconds and 3 microseconds. Its help page states: "The result will be in UTC, not the local time zone of your spreadsheet" (support.google.com). For Solscan's Block Time that is =EPOCHTODATE(A2,1). We have not tested this function or our workbook in Google Sheets.
| Block Time | Human Time | Date only | Date and time |
|---|---|---|---|
| 1779128572 | 2026-05-18T18:22:52.000Z | 2026-05-18 | 2026-05-18 18:22:52 |
| 1767223800 | 2025-12-31T23:30:00.000Z | 2025-12-31 | 2025-12-31 23:30:00 |
| 1767225600 | 2026-01-01T00:00:00.000Z | 2026-01-01 | 2026-01-01 00:00:00 |
The Block Time formula and the Human Time formula gave the same dates on every row.
The second row is 23:30 UTC on 31 December. In a time zone one hour ahead of UTC, the same moment is 00:30 on 1 January. We tested that too: =(A3+3600)/86400+DATE(1970,1,1) returns 2026-01-01 00:30.
The Nah Crypto Tax Tracker workbook's Instructions say: "Year-end uses the date you enter; use UTC timestamps consistently." We entered an EXAMPLE SOL sale (bought for 150 plus a 0.10 fee, sold for 125 minus a 0.10 fee) both ways:
The workbook takes whatever date you enter; it can't tell which convention you used. Pick one, use it for every row, and write it in Notes (H) on the first row, e.g. "all dates UTC from Solscan Block Time". Which convention fits your situation is a question for a tax professional.
We also pasted the raw Human Time text into the Date column. The workbook could not read it as a date: the Check column flagged the row "CHECK DATE (not a real date)", the Year column stayed blank, and the Summary's "Rows needing attention" counter went to 1. The sale was left out of FIFO and out of every year in the per-year Summary, so the SOL holding still showed 1 as if nothing had been sold. A text date is easy to miss, so check after every paste that column M says OK on every row and that the counter is 0. The workbook's Instructions ask for real dates (YYYY-MM-DD) for this reason.
The Nah Crypto Tax Tracker is an .xlsx plus a PDF guide with plain formulas and no macros: Buy/Sell rows, Tx hash in G, Notes in H, FIFO by date then row order, an OVERSOLD flag and a per-year Summary for 2024 to 2030. FIFO only; not tailored to any country's tax rules. 29 USDC one-time: Nah Crypto Tax Tracker. For the export itself, see exporting Solana DEX history to CSV. Not tax advice.
Not affiliated with Solscan, Microsoft, Google or The Document Foundation (LibreOffice). Sources checked 21 October 2026.