12:13:37 For this one, the first two lines in the file header read: generated_at_cst is 2026-11-14 12:13:37 UTC+8, and generated_at_utc is 2026-11-14 04:13:37 UTC. The seconds match, and the dates are the same.
Earlier, when the two lines fell on different dates, I jotted down a rule: whenever I see utc, move it back one day. Later, when I came across one where they fell on the same day, I thought about adding a starting point to that rule—after what time should I stop moving it back? I stopped halfway through. I’d be the one drawing that line, and the interface only returns the two original lines; it doesn’t provide that column. These are just personal records of my readings, not investment advice; neither the conversions nor the cutoff go into the table, and the dates are copied exactly as written by the interface.
Under market, total_market_cap_usd 2280952479254.5874, btc_dominance_pct 58.71, and market_cap_change_24h_pct -5.04 are all attached to the time this data was retrieved, with no date columns of their own. The numbers aren’t formatted consistently either, so I store each one as is.
Earlier, when the two lines fell on different dates, I jotted down a rule: whenever I see utc, move it back one day. Later, when I came across one where they fell on the same day, I thought about adding a starting point to that rule—after what time should I stop moving it back? I stopped halfway through. I’d be the one drawing that line, and the interface only returns the two original lines; it doesn’t provide that column. These are just personal records of my readings, not investment advice; neither the conversions nor the cutoff go into the table, and the dates are copied exactly as written by the interface.
Under market, total_market_cap_usd 2280952479254.5874, btc_dominance_pct 58.71, and market_cap_change_24h_pct -5.04 are all attached to the time this data was retrieved, with no date columns of their own. The numbers aren’t formatted consistently either, so I store each one as is.