Hex timestamp to date
For example, 0x6553f400 is Tue, Nov 14, 2023, 10:26:08 PM UTC, which is 2023-11-14T22:26:08.000Z in ISO 8601 and 1700000768 in Unix seconds.
Hex for 1700000768, read as seconds since the Unix epoch.
Detected: Hex timestamp/t/0x6553f400
Your timezone
UTC · GMT+00:00 · UTC
Tue, Nov 14, 2023, 10:26:08 PM
Common formats
UTC
Tue, Nov 14, 2023, 10:26:08 PM
ISO 8601
2023-11-14T22:26:08.000Z
Unix (seconds)
1700000768
Unix (millis)
1700000768000
Relative
…
Timestamps show up in hex all the time: packet captures, registry values, embedded-device dumps, git internals, and debugger output. An 8-digit hex value like 0x6553f400 is usually 32-bit Unix seconds; 11 digits is typically milliseconds. Paste one below (with or without the 0x) and parsetime converts it and tells you which unit it inferred.
Do it with the API
curl https://parsetime.dev/api/t/0x6553f400?format=hexThe same conversion as JSON: no key, no signup, permissive CORS. Try this call or read the API docs.
Common questions
- How do I know if a hex timestamp is seconds or milliseconds?
- By size: 8 hex digits (fits in 32 bits) is almost always seconds, and 11 hex digits is milliseconds for current dates. parsetime infers the unit from the decoded magnitude and says which it chose.
- How do I convert hex to a date on the command line?
- date -r $((16#6553f400)) on macOS, or date -d @$((16#6553f400)) on Linux. The $((16#…)) form converts hex to decimal in bash.
- What is 0xFFFFFFFF as a date?
- February 7, 2106, at 06:28:15 UTC. It's the largest value an unsigned 32-bit seconds field can hold. (The signed version caps out earlier, at 0x7FFFFFFF, which is the Year 2038 problem.)