Crypto Tracking Spreadsheet

Originally published · 4 min read · Updated

Download a crypto tracking spreadsheet built for wallet actions, approvals, source evidence, costs, exits, and review dates rather than price watching.

TL;DR: Track each wallet action with its transaction hash, source, approval, exit condition, and next review date; a portfolio balance cannot reconstruct those facts.

crypto spreadsheetwallet trackingDeFi recordsairdrop tracking
Table of contents

An analyst-grade spreadsheet connecting wallet activity, costs, and exit dates

A useful crypto tracking spreadsheet needs at least 15 fields: UTC date, wallet alias, chain, protocol, action, asset, amount, transaction hash, approval spender, approval limit, source URL, exit condition, next review time, status, and notes.

Download the crypto tracking spreadsheet CSV. It opens in Excel, Google Sheets, LibreOffice, and Numbers.

Crypto portfolio tracking spreadsheet fields

FieldWhat to enterWhy it earns a column
date_utcISO timestampBlockchains and campaign cutoffs use time zones precisely
wallet_aliasActivity wallet name, never a seed phraseShows which key owns the action
chainExact networkThe same address can have different approvals per chain
protocolProduct usedGroups positions and incidents
actionDeposit, swap, bridge, approve, unstake, claimMakes the record operational
asset, amountToken symbol and quantityReconstructs exposure without relying on today's USD price
tx_hashExplorer transaction hashVerifiable execution evidence
approval_spender, approval_limitContract and capReveals permissions that survive the position
source_urlOfficial rule or docs pagePreserves the reason for the action
exit_conditionObservable triggerTurns monitoring into a decision
next_review_utcScheduled checkPrevents abandoned approvals and positions
statusPlanned, open, queued, closed, failedSeparates intent from execution

A transaction hash alone is not a record. It shows what executed, not which rule you relied on, what you approved, or when you planned to exit.

Crypto trading spreadsheet formulas

Add four calculated columns when you need performance:

net_cash_flow = proceeds + rewards_sold - deposits - gas - bridge_fees - trading_fees - funding

net_pnl = current_exit_value + cumulative_net_cash_flow

roi = net_pnl / capital_deployed

capital_days = eligible_balance x days_eligible

Capital-days is more useful than points for cross-program comparison because dollars and days share a real unit; points from two protocols do not.

Keep realized rewards separate from displayed points. Until points can be claimed and sold, their realized value is $0.

Airdrop tracking spreadsheet example

Suppose wallet activity-01 bridges 500 USDC to Base, approves a lending market for 500 USDC, and deposits 450 USDC.

Use three rows, not one:

  1. Bridge: source transaction, bridge route, destination asset contract, $ cost.
  2. Approval: spender contract, allowance, and planned revoke date.
  3. Deposit: market contract, receipt asset, exit condition, and review time.

If the protocol changes its points rules, update the source and add a new dated note; do not overwrite the evidence used for the original decision.

Crypto tax spreadsheet limits

This template is an operational ledger, not a complete tax lot system. Tax accounting may need acquisition basis, disposal proceeds, lot-selection method, fair market value at receipt, transaction classification, and jurisdiction-specific treatment.

Do not infer tax basis from current wallet balances. Transfers between your own wallets can look like disposals to a naive importer, and DeFi receipt tokens can create transactions that require separate classification. Export raw exchange and wallet histories before a platform's retention period expires and consult a qualified local professional for tax treatment.

How to keep a crypto spreadsheet useful

  • Use UTC and ISO dates such as 2026-07-18T14:30:00Z.
  • Use wallet aliases in shared files; keep addresses in a protected lookup if needed.
  • Link official docs, not screenshots or influencer summaries.
  • Never store seed phrases, private keys, API secrets, or recovery codes.
  • Protect formulas and validation columns from accidental edits.
  • Keep an append-only raw export separate from the working view.
  • Review queued withdrawals and unlimited approvals weekly.

Our strongest opinion: price is the least irreplaceable field. A market data service can rebuild price history; it cannot recover a deleted rule page or explain why you approved an unknown spender.

Use crypto due diligence to define stop conditions and token approval checker for the permission audit.

Sources