Interprete a UUID

Back

UUID: 
Your input:                      e3626a3a-8205-8a0f-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:e3626a3a-8205-8a0f-87e9-5ce32bd83b97
URI:                             uuid:e3626a3a-8205-8a0f-87e9-5ce32bd83b97
Microsoft GUID syntax:           {E3626A3A-8205-8A0F-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xe3626a3a, 0x8205, 0x8a0f, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.302245754706203477040098900350321834903
As OID (Microsoft):              1.2.840.113556.1.8000.2554.58210.27194.33285.35343.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.16384775193849334287.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3814877754.2181401103.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.58210.27194.33285.35343.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xe3626a3a8205a0f07e95ce32bd83b97]
Custom data block1 (32 bit):     [0xe3626a3a]
Custom data block2 (16 bit):     [0x8205]
Custom data block3 (12 bit):     [0xa0f]
Custom data block4 (14 bit):     [0x07e9]
Custom data block5 (48 bit):     [0x5ce32bd83b97]

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

Random 16 bits:                  [0xe362] 0b1110001101100010
Milliseconds:                    [0x6a] 415 (deviation -2ms..2ms)
Seconds:                         [0x3a] 58
Minute of day:                   [0x0582] 1410 (23:29)
Day of year:                     [0x0fa] 250 (Day=7, Month=9)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-09-07 23:29:58'415 (deviation -2ms..2ms)