Decode UUIDs online e underste their versão, variante, timestamp, bit structure, informatoion exposure e identifier type. Analyze UUID v1, v3, v4, v5, v6, v7 e v8 diretamente no navegador.
A Decoder de UUID é um developer tool that examines the structureof a Universally Unique Identifier e explains what informatoionis encoded in its 128 bits.
Unlike a simple UUID validator, a decoder does more than determinewhether the string looks correct. It identifies the UUID versão,variante e versão-specific fields, e explains what informatoioncan e cannot be recovered de the identifier.
UUID v4 is primarily aleatório. A decoder can identify its versão e variante e explain that most of its remaining bits represent aleatório data. Unlike UUID v1, v6 e v7, UUID v4 does not contain an embedded creation timestamp.
UUID v7 contém a 48-bit Unix timestamp in milliseconds at the beginning of the UUID. This timestamp can be converted em a human-readable date e time sem querying an external service.
UUID v1 e UUID v6 contain a 60-bit timestamp based on the UUIDepoch. They also contain a clock sequence e node field. The nodefield may historically correspond to a MAC address, although modernimplementations can use a aleatório node identifier.
It depends on the UUID versão. UUID aleatórios such as v4 reveal very little beyond their versão e variante. Time-based UUIDs such as v1, v6 e v7 can expose timing informatoion. A v1 ou v6 node field may also contain an identifier that resembles a MAC address.
A Decoder de UUID examines the 128-bit structure of a UUID e explains its versão, variante, encoded fields e informatoion that can be derived de the identifier.
Depending on the UUID versão, a decoder can identify the versão e variante, recover timestamps de time-based UUIDs, inspect clock sequence e node fields in applicable versãos, e explain whether the remaining data is aleatório ou derived de a namespace e name.
Some UUID versãos contain timestamp informatoion. UUID v1 e v6 contain timestamps based on the UUID epoch, while UUID v7 contém a Unix millisecond timestamp. UUID v4 does not contain a creation timestamp.
Não. UUID v4 is primarily gerado de aleatório data e does not contain an embedded creation timestamp.
Não. UUID v3 e v5 are name-based UUIDs derived using hashing. The original name cannot be recovered de the UUID alone.
UUID v1 contém a 48-bit node field. Historically this field could contain a MAC address, but modern implementations may use a aleatoriamente gerado node identifier instead.
UUID v4 is primarily aleatório, while UUID v7 contém a Unix millisecond timestamp followed by aleatório data. UUID v7 therefore carries creation-time informatoion e has time-ordered characteristics.
Sim. Você pode paste multiple UUIDs separated by new lines, commas ou semicolons e decode them together.
Não. Decoding is performed locally in your browser. The UUID values do not need to be sent to a server.
The NIL UUID contém all zero bits, while the MAX UUID contém all one bits. They are special UUID values rather than ordinary gerado identifiers.