Seeing all three time-based RFC 9562 versions side by side across two timestamps two minutes apart illustrates why UUID v7 and UUID v6 preserve strict chronological sort order while UUID v1 fragments database indexes.
Consider the RFC 9562 reference instant 2022-02-22T19:22:22.000Z (Unix Epoch 1,645,557,742,000 ms = 0x017f22e279b0; Gregorian 100-ns count 138,648,505,420,000,000 = 0x1ec9414c232ab00) and a second timestamp 120 seconds later at 2022-02-22T19:24:22.000Z (Unix 0x017f22e44e70; Gregorian 0x1ec941509b93700):
# T + 0s (2022-02-22T19:22:22.000Z)
UUID v7 : 017f22e2-79b0-7cc3-98c4-dc0c0c07398f
UUID v6 : 1ec9414c-232a-6b00-b3c8-9f6bdeced846
UUID v1 : c232ab00-9414-11ec-b3c8-9f6bdeced846
# T + 120s (2022-02-22T19:24:22.000Z)
UUID v7 : 017f22e4-4e70-7a19-8f21-4b90e12c5d3a (017f22e4 sorts AFTER 017f22e2)
UUID v6 : 1ec94150-9b93-6700-b3c8-9f6bdeced846 (1ec94150 sorts AFTER 1ec9414c)
UUID v1 : 09b93700-9415-11ec-b3c8-9f6bdeced846 (09b93700 sorts BEFORE c232ab00!)
Because UUID v1 stores time_low (the fastest-changing 32 bits of the 100-nanosecond clock) in octets 0–3, its leading 8 hex digits overflow every 2^32 x 100 ns = 429.4967296 seconds (~7 minutes 9.5 seconds), jumping back to 00000000-... and scattering inserts across historical B-tree pages. Both UUID v7 and UUID v6 store the most-significant timestamp bits in octets 0–5, making raw byte order (memcmp) and ASCII lexicographical order monotonically increasing:
[
"0195a0b4-3c10-71a4-9c02-54e81a09f3b1",
"0195a0b4-3c11-78f0-a41d-8e2c77140b6e",
"0195a0b4-3c12-732b-89e5-1c4f0a68d290"
]
To verify or extract the exact UTC creation timestamp from any generated v7, v6, or v1 identifier, paste the key into the UUID Parser & Decoder.