Interpret a UUID

Back

Your input:                      d7e3a719-0e00-8504-87ea-5ce32bd83b97

Various notations:

URN:                             urn:uuid:d7e3a719-0e00-8504-87ea-5ce32bd83b97
URI:                             uuid:d7e3a719-0e00-8504-87ea-5ce32bd83b97
Microsoft GUID syntax:           {D7E3A719-0E00-8504-87EA-5CE32BD83B97}
C++ struct syntax:               { 0xd7e3a719, 0x0e00, 0x8504, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.286966059628085609527385951046802619287
As OID (Microsoft):              1.2.840.113556.1.8000.2554.55267.42777.3584.34052.34794.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.15556461263918761220.9793742470433487767
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3622020889.234915076.2280283363.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.55267.42777.3584.34052.34794.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xd7e3a7190e0050407ea5ce32bd83b97]
Custom data block1 (32 bit):     [0xd7e3a719]
Custom data block2 (16 bit):     [0x0e00]
Custom data block3 (12 bit):     [0x504]
Custom data block4 (14 bit):     [0x07ea]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3

Random 16 bits:                  [0xd7e3] 0b1101011111100011
Milliseconds:                    [0xa7] 654 (deviation -2ms..2ms)
Seconds:                         [0x19] 25
Minute of day:                   [0x000e] 14 (00:13)
Day of year:                     [0x045] 69 (Day=10, Month=3)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7ea] 2026
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2026-03-10 00:13:25'654 (deviation -2ms..2ms)