Interpret a UUID
Back
Your input: dd6e7629-dc01-8c0b-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:dd6e7629-dc01-8c0b-87ea-5ce32bd83b97
URI: uuid:dd6e7629-dc01-8c0b-87ea-5ce32bd83b97
Microsoft GUID syntax: {DD6E7629-DC01-8C0B-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdd6e7629, 0xdc01, 0x8c0b, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.294332936363681705363358640809319086999
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56686.30249.56321.35851.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15955820451977071627.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3715003945.3691088907.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56686.30249.56321.35851.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdd6e7629dc01c0b07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdd6e7629]
Custom data block2 (16 bit): [0xdc01]
Custom data block3 (12 bit): [0xc0b]
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: [0xdd6e] 0b1101110101101110
Milliseconds: [0x76] 462 (deviation -2ms..2ms)
Seconds: [0x29] 41
Minute of day: [0x01dc] 476 (07:55)
Day of year: [0x0bc] 188 (Day=7, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-07 07:55:41'462 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing