Interprete a UUID

Back

UUID: 
Your input:                      eaca7009-02e2-8164-87e8-5ce32bd83b96

Various notations:

URN:                             urn:uuid:eaca7009-02e2-8164-87e8-5ce32bd83b96
URI:                             uuid:eaca7009-02e2-8164-87e8-5ce32bd83b96
Microsoft GUID syntax:           {EACA7009-02E2-8164-87E8-5CE32BD83B96}
C++ struct syntax:               { 0xeaca7009, 0x02e2, 0x8164, { 0x87, 0xe8, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x96 } }

As OID (ISO/ITU-T 128 bits):     2.25.312090467322916219350540006204743629718
As OID (Microsoft):              1.2.840.113556.1.8000.2554.60106.28681.738.33124.34792.6087467.14171030
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.16918458134176104804.9793179520480066454
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3939135497.48398692.2280152291.735591318
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.60106.28681.738.33124.34792.23779.11224.15254

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xeaca700902e216407e85ce32bd83b96]
Custom data block1 (32 bit):     [0xeaca7009]
Custom data block2 (16 bit):     [0x02e2]
Custom data block3 (12 bit):     [0x164]
Custom data block4 (14 bit):     [0x07e8]
Custom data block5 (48 bit):     [0x5ce32bd83b96]

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

Random 16 bits:                  [0xeaca] 0b1110101011001010
Milliseconds:                    [0x70] 439 (deviation -2ms..2ms)
Seconds:                         [0x09] 9
Minute of day:                   [0x02e2] 738 (12:17)
Day of year:                     [0x164] 356 (Day=21, Month=12)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e8] 2024
Signature:                       [0x5ce32bd83b96] HickelSOFT "SQL Server Sortable Custom UUID", Version 2 (very likely)
UTC Date Time:                   2024-12-21 12:17:09'439 (deviation -2ms..2ms)