UUID/GUID numbers decoder
Calculator analyzes your UUID/GUID number. If it's a correct UUID then it tries to detect used UUID version scheme.

Beta version#

This online calculator is currently under heavy development. It may or it may NOT work correctly.
You CAN try to use it. You CAN even get the proper results.
However, please VERIFY all results on your own, as the level of completion of this item is NOT CONFIRMED.
Feel free to send any ideas and comments !

Calculations data: Enter your UUID/GUID number here#

Your UUID/GUID number here

Results: What we can say about your UUID/GUID number#

Validation and version
Is it correct UUID versionyes
Detected RFC versionversion 1 (timestamp + MAC address)
Variant (revision)9
Detected RFC variant scheme10xx - DCE 1.1, ISO/IEC 11578:1996
UUID written in various forms
UUID in text formata3e4f906-e725-11eb-94f9-bbf63fdaac38
UUID as one hexadecimial number0xa3e4f906e72511eb94f9bbf63fdaac38
UUID as one decimall number217853057863583364484153428529316015160
UUID as raw bytes
All bytes (16 bytes)a3 e4 f9 06 e7 25 11 eb 94 f9 bb f6 3f da ac 38
time_low (4 bytes)a3 e4 f9 06
time_mid (2 bytes)e7 25
time_hi_and_version (2 bytes)11 eb
clock_seq_hi_and_res (1 byte)94
clock_seq_low (1 byte)f9
node (6 bytes)bb f6 3f da ac 38
60-bit timestamp
Timestamp as one hexadecimal number0x1ebe725a3e4f906
Timestamp as one decimal number138458362414430470
Decoded timestamp in human readable form (UTC)2021-07-17 17:37:21.443.047.000
UTC time in ISO format2021-07-17T17:37:21.443Z
Remaining nanoseconds impossible to encode into ISO date47000
14-bit clock sequence
Clock sequence as hexadecimal number0x14f9
Clock sequence as decimal number5369
48-bit node identifier
MAC address (6 bytes)bb:f6:3f:da:ac:38
Multicast bit enabledyes

Some facts#

  • The UUID is a Universally Unique IDentifier. We can use it to identify objects in the global space.
  • UUID number consists of 128 bits which corresponds to 16 bytes.
  • UUID in text format is usually written as 32 characters separated by dashes which corresponds to the values ​​of subsequent bytes in hexadecimal system starting with the most significant (the so-called big endian order) e.g.

  • The UUID format is standarized in RFC 4122 document.
  • The meaning of individual bytes is different depending on the version and variant (sometimes called a revision) used. RFC 4122 defines 5 versions:
    • version 1 - based on a 60-bit time stamp and 48-bit MAC address,
    • version 2 - modification of version 1 intended for DCE security standards,
    • version 3 - based on the MD5 hash of a known name, e.g. domain or URL, but the meaning of the name is not imposed by the specification,
    • version 4 - based entirely on random numbers or pseudorandom,
    • version 5 - modification of version 3 using the hash function SHA-1.
  • A sample UUID in version 1 contains:
    f68b5140time_low4 bytesed89time_mid2 bytes11ebtime_high_and_version2 bytesa44cclock_seq_and_res2 bytes69d32820f390node6 bytes \underbrace{\overbrace{f68b5140}^{\text{time\_low}}}_{\text{4 bytes}} - \underbrace{\overbrace{ed89}^{\text{time\_mid}}}_{\text{2 bytes}} - \underbrace{\overbrace{11eb}^{\text{time\_high\_and\_version}}}_{\text{2 bytes}} - \underbrace{\overbrace{a44c}^{\text{clock\_seq\_and\_res}}}_{\text{2 bytes}} - \underbrace{\overbrace{69d32820f390}^{\text{node}}}_{\text{6 bytes}}
    • time_low - the least significant 32 bits of the 60-bit timestamp (0xf68b5140),
    • time_mid - next 16 bits of the 60-bit timestamp (0xed89) ,
    • time_high_and_version - the most significant 12 bits of the 60-bit timestamp and 4-bit version number (0x11eb),
    • clock_seq_and_res - 14-bit clock sequence and variant number (0xa44),
    • node - 48-bit (6 byte) MAC address (0x69d32820f390 or 69:d3:28:20:f3:90).
  • The UUID timestamp encoded in versions 1 and 2 is 60 bits. It corresponds to the number of 100 nanosecond intervals since October 15, 1582 which corresponds to the beginning of the Gregorian calendar.
  • Versions 1 and 2 contain the encoded 48-bit MAC address of the host, where the UUID was generated. When the MAC address is unavailable, it is allowed to use a random number - in this case the generated number should have the multicast bit set.
  • The uniqueness of UUID numbers is based on low probability of collision. Versions 1 and 2 also use the MAC address of the host, which is assumed to uniquely identify the network device in the global scale.

Tags and links to this website#

What tags this calculator has#


This is permalink. Permalink is the link containing your input data. Just copy it and share your work with friends:

Links to external sites (leaving Calculla?)#

JavaScript failed !
So this is static version of this website.
This website works a lot better in JavaScript enabled browser.
Please enable JavaScript.