THE QUICK ANSWER
Enter one timestamp, status and note per line. The tool sorts your supplied events, converts them to UTC and exports the record; it does not fetch or verify transaction status.
01
Enter the events you can document
Use one line per event in the form timestamp | status | reference or note. Keep exactly two separator bars on each line, and include a status. The final note may be empty; do not put another | character inside it.
Supply 1 to 250 events. Start with the exact observed status, rather than a conclusion such as “payment lost”. Give the marketplace order, Steam offer and external payout their own references when they are different records.
Different clocks, one chronological record
15:00 UTC
2026-10-23T15:00:00Z — example offer sent.
11:12 at -04:00
The same-day local entry converts to 15:12 UTC.
Sorted export
Both entries use Z in the downloaded timeline.
Original illustration using invented event times; it demonstrates normalization, not a real trade.
Original explanation · not an account screenshotTry it with your own details.
This tool keeps your input in this page. It does not upload it, add it to the address or save it. Downloads happen only when you choose them. Reset the form when you finish.
| First event | 2026-10-23T15:00:00Z | Offer sent | Example offer A |
|---|---|
| Another source clock | 2026-10-23T11:12:00-04:00 | Accepted | Example offer A |
| What they mean | The second event is 15:12 UTC, twelve minutes after the first. These are invented example events. |
02
Include the offset from each original record
Accepted timestamps use a full date, T, hour and minute, optional whole seconds, then Z or an explicit offset such as -04:00. For example, 2026-10-23T15:00:00Z and 2026-10-23T11:00:00-04:00 describe the same instant.
A date alone, “3 pm”, EST or a place name is not an accepted input. The form also excludes fractional seconds. If the source does not state a time zone, leave that uncertainty in your notes and establish it before assigning an exact offset.
03
Read the sorted timeline without adding a diagnosis
Build the timeline to order the supplied events from earliest to latest. Equal timestamps keep their original input order; the tool cannot determine which of simultaneous recorded events caused the other.
Output timestamps use UTC with Z. Statuses and notes remain your entries. The tool does not contact Steam, a partner, a bank or a blockchain, and sorting “Sent” before “Received” does not verify delivery. Steam’s own Trade Offers history remains the source for the actual offer record.
Keep three references attached to their own stages
Order event
Marketplace order reference and displayed status.
Steam event
Actual offer reference and its observed state.
Payout event
External payment reference, if one was created.
The timeline preserves supplied records; its order does not verify any stage or transfer.
Original explanation · not an account screenshot04
Download the record you intend to share
Choose transaction-timeline.csv for a table or transaction-timeline.txt for a readable sequence. The CSV has timestamp_utc, status and reference_or_note columns. These are export columns, not a raw Steam history import format.
Review references and notes before attaching either file to a support case. The tool does not save or upload your input. Download a copy only if you need it, then use Reset this form when finished. Nothing is submitted to support by this tool.
BEFORE YOU CONTINUE
Quick checklist
- Use 1–250 events with exactly three bar-separated fields.
- Give every timestamp Z or an explicit UTC offset.
- Keep each real order, offer or payout reference with its event.
- Check the UTC result and downloaded file before sharing.
Official sources
Tool behaviour was checked against StrikePot’s form and browser implementation on 26 October 2026 (America/Toronto). The external references below explain the relevant formats and source records.
- MDN — Date.parse: explicit time zones and standard date-time strings · reviewed
- Steam Support — Steam Trade Offers: pending offers and offer history · reviewed
Implementation inspected: scripts/growth_tools_build.py timeline form and source/js/growth-tools.js gtTimestamp, gtTimeline, gtCSVOutput and timeline submit handler. Limits, exact field separators, stable ordering and download names come from that code, not a provider promise. Current indexed Steam Help text was read; direct Help extraction returned an image-only body. No account history was fetched and no live transaction was checked. Example events are invented.
