Kraken trade history chart
This guide is for Kraken and Kraken Pro traders who want their real fills on the chart instead of buried in the History table. Export your trades from Kraken, map the fill rows into KLinePic's CSV schema, and render a shareable review image with entry/exit (B/S) markers, holding window, return, max run-up, max drawdown, and optional indicators such as MACD.
KLinePic is free to start and needs no account to render — the loop from export to review image takes minutes.
Kraken and Kraken Pro let you download your history as a CSV file. The exact menu labels and options change over time, so treat the steps below as a general path and confirm the current wording in Kraken's official help center rather than memorizing a click path.
If you only see a Ledgers export, that is fine — you will simply filter it down to trade rows in the next step.
Kraken's exports document the report types but headers can differ between a Trades file and a Ledgers file — treat this as a checklist against your export's typical columns. The target schema is fixed: KLinePic reads trade_id, symbol, event_type, position_side, time, price, quantity, fee, note, documented in the data protocol. Extra columns are ignored on import and listed back to you; copy details such as the fee currency into note only when you want them preserved in the normalized record.
One Kraken-specific detail matters more than the rest: Kraken denotes Bitcoin as XBT, not BTC. Pairs appear as XBT/USD or XBTUSD, and native pair codes can look like XXBTZUSD with extra X/Z asset prefixes. A raw Trades export often looks like this (note it uses Kraken's own headers, not the KLinePic schema):
txid,ordertxid,pair,time,type,ordertype,price,cost,fee,vol TQ7A2B-XBT01,OABCDE-11111,XXBTZUSD,2026-05-10 09:15:00,buy,limit,61250.00,6125.00,6.13,0.1000 TQ9C4D-XBT02,OFGHIJ-22222,XXBTZUSD,2026-05-10 18:45:00,sell,limit,62880.00,6288.00,6.29,0.1000
Normalize that symbol to one consistent value KLinePic can match to a candle series — the table below shows the direction of each field.
| KLinePic field | Your export's typical column | Notes |
|---|---|---|
| trade_id | Usually none — create your own | One stable id per round-trip trade; entry and exit fills share it. Kraken's txid is per fill, so it is not a round-trip id. |
| symbol | Pair / market column | Kraken uses XBT for Bitcoin (XBT/USD, XXBTZUSD). Normalize to one consistent symbol such as XBTUSD across every row of a trade. |
| event_type | Type / side column | Normalize to lowercase buy or sell. |
| position_side | Futures direction, if present | Spot can default to long; Kraken Futures needs explicit long / short. |
| time | Time column | Kraken CSV time is typically UTC; write explicit offsets like +00:00. |
| price | Price column | Use the executed fill price, not the order's limit price. |
| quantity | Volume / vol column | Base units (0.1 XBT), not the quote cost total in USD. |
| fee | Fee column | Optional, but useful for honest net-return journaling. |
| note | Fee currency / free text | Optional. There is no fee_asset column in KLinePic — keep the fee currency as note text such as fee_asset=USD, or drop it. |
A complete Kraken round-trip trade — one buy, one sell, same trade_id — looks like this after mapping. Note the symbol is normalized to a single Kraken token (XBTUSD):
trade_id,symbol,event_type,position_side,time,price,quantity,fee,note KRAKEN-XBT-001,BTCUSDT,buy,long,2026-05-10T09:15:00+00:00,61250.00,0.1,6.13,fee_asset=USD KRAKEN-XBT-001,BTCUSDT,sell,long,2026-05-10T18:45:00+00:00,62880.00,0.1,6.29,fee_asset=USD
Scaling in or out simply adds more rows with the same id. The crypto exchange template ships this exact header so you can paste mapped rows straight in.
| KLinePic | Manual screenshot + spreadsheet | Typical trading-journal SaaS | |
|---|---|---|---|
| Setup time | Minutes: export, map, paste | Slow, repeated by hand per trade | Onboarding plus per-exchange import setup |
| Account required | No account needed to render | None | Usually requires sign-up first |
| Output | Annotated K-line image with trade metrics | Static screenshot plus separate numbers | Web dashboards and statistics |
| Buy/sell markers on real K-line | Yes, B/S at actual fill price and time | Drawn manually, easy to misplace | Varies by product and plan |
| Shareable image | Yes, the chart itself is the deliverable | Screenshots without computed context | Often screenshots of dashboards |
| Cost to start | Free to start | Free, but pays in time | Commonly subscription-based |
Kraken labels Bitcoin as XBT (XBT/USD, XXBTZUSD). Leave the raw code in place and it may not match the candle series you expect. Normalize the symbol consistently to what KLinePic expects — one token such as XBTUSD — across every row of the trade.
Kraken CSV time is typically UTC. Chart those times as local and every marker shifts by hours. Encode the offset explicitly — +00:00 — in time after confirming the format in your export.
A Ledgers export includes deposits, withdrawals, transfers, and rewards. Those have no fill price and must be removed, or they become false markers. Keep executed trade rows only.
One order can execute as several fills, each with its own txid. Keep the rows but give them one trade_id; otherwise a single scale-in reads as several unrelated trades.
Kraken exports carry both the base vol and the quote cost. quantity must be the base amount (0.1 XBT), not the USD value of the fill.
Futures history is a separate export and a different product. Map its rows to their own symbol, carry an explicit long/short, and never merge them into a spot trade.
Export your trades from Kraken, map them into KLinePic's CSV fields (trade_id, symbol, event_type, position_side, time, price, quantity, fee, note), then upload or paste the CSV to render. No account is needed.
Yes. Once each row has symbol, side, time, price, and size, spot and derivatives fills render the same way. Kraken Futures is a separate export from spot, and derivatives rows should carry an explicit position_side.
Kraken denotes Bitcoin as XBT, so pairs appear as XBT/USD rather than BTC/USD, and native codes may look like XXBTZUSD. Normalize the symbol consistently to what KLinePic expects before rendering, so markers resolve to one candle series.
Kraken CSV exports typically record time in UTC; confirm the format in your export, then write it into time as an explicit offset such as 2026-05-10T09:15:00+00:00 so markers land on the correct candles.
No. The CSV download is enough; KLinePic renders from an uploaded or pasted file. For automation there is a documented Agent API and a CSV/JSON data protocol.
Yes. Batch rendering is supported — a month of Kraken trades becomes a full set of review images in one pass, via the web UI or the documented Agent API.