Interprete a UUID

Back

UUID: 
Your input:                      e4d62d1e-b300-870b-87e9-5ce32bd83b97

Various notations:

URN:                             urn:uuid:e4d62d1e-b300-870b-87e9-5ce32bd83b97
URI:                             uuid:e4d62d1e-b300-870b-87e9-5ce32bd83b97
Microsoft GUID syntax:           {E4D62D1E-B300-870B-87E9-5CE32BD83B97}
C++ struct syntax:               { 0xe4d62d1e, 0xb300, 0x870b, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }

As OID (ISO/ITU-T 128 bits):     2.25.304176049707362766377876341901099547543
As OID (Microsoft):              1.2.840.113556.1.8000.2554.58582.11550.45824.34571.34793.6087467.14171031
As OID (Waterjuice 2x64 bits):   1.3.6.1.4.1.54392.1.16489416695539074827.9793460995456777111
As OID (Waterjuice 4x32 bits):   1.3.6.1.4.1.54392.2.3839241502.3003156235.2280217827.735591319
As OID (Waterjuice 8x16 bits):   1.3.6.1.4.1.54392.3.58582.11550.45824.34571.34793.23779.11224.15255

Interpretation of the UUID:

Variant:                         [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version:                         [0x8] Custom implementation
Custom data:                     [0xe4d62d1eb30070b07e95ce32bd83b97]
Custom data block1 (32 bit):     [0xe4d62d1e]
Custom data block2 (16 bit):     [0xb300]
Custom data block3 (12 bit):     [0x70b]
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:                  [0xe4d6] 0b1110010011010110
Milliseconds:                    [0x2d] 176 (deviation -2ms..2ms)
Seconds:                         [0x1e] 30
Minute of day:                   [0x00b3] 179 (02:58)
Day of year:                     [0x0b7] 183 (Day=2, Month=7)
Unused 2 bits:                   [0] 0b00
Year:                            [0x7e9] 2025
Signature:                       [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time:                   2025-07-02 02:58:30'176 (deviation -2ms..2ms)