Interpret a UUID
Back
Your input: dcca3d3b-8e01-8d0f-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:dcca3d3b-8e01-8d0f-87ea-5ce32bd83b97
URI: uuid:dcca3d3b-8e01-8d0f-87ea-5ce32bd83b97
Microsoft GUID syntax: {DCCA3D3B-8E01-8D0F-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdcca3d3b, 0x8e01, 0x8d0f, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.293480244983501684773912094905745292183
As OID (Microsoft): 1.2.840.113556.1.8000.2554.56522.15675.36353.36111.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.15909595959634529551.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3704241467.2382466319.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.56522.15675.36353.36111.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdcca3d3b8e01d0f07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdcca3d3b]
Custom data block2 (16 bit): [0x8e01]
Custom data block3 (12 bit): [0xd0f]
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: [0xdcca] 0b1101110011001010
Milliseconds: [0x3d] 239 (deviation -2ms..2ms)
Seconds: [0x3b] 59
Minute of day: [0x018e] 398 (06:37)
Day of year: [0x0fd] 253 (Day=10, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-10 06:37:59'239 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing