A name, down to the byte.

Turn a label into a Celestia namespace. Decode an existing ID, inspect its bytes and check its activity.

29 BYTES
ONE NAMESPACE

Namespace workbench

Your label

8 / 10 bytes

Capacity is measured in UTF-8 bytes. One 月 uses 3 bytes. Spaces count too.

Try

Show byte offsets in the diagram

Version 0 layout
1 version byte + 18 zero prefix bytes + 10 payload bytes. Short labels are padded with zeros on the left. Your text is encoded as entered, including spaces.

Your namespace

29 bytes · 58 hex characters

Export & Integrate

Your namespace, byte by byte

Version · 1 Prefix · 18 Payload · 10

Hover or focus a byte group to follow it between the hex and diagram.

Has this namespace posted blobs?

Run a lookup for this exact namespace.

Mainnet namespace census

How much of the payload do people use?

All namespace records, fetched page by page from Celenium.

0Namespace records scanned

0Standard v0, nonempty payload

0%ASCII among UTF-8 payloads

0%Multibyte among UTF-8 payloads

Ready to fetch Mainnet namespaces.

The chart counts standard version-0 payloads after removing leading zero padding, including binary payloads. Text percentages use only payloads that decode as UTF-8. Reserved IDs remain included.

Real namespaces on mainnet right now

Examples will appear from the loaded records, with different payload lengths.

Reserved namespace reference

Version-0 IDs whose significant payload fits in one byte fall in the primary reserved range. The values below name specific entries; the remaining values in that range are reserved too.

Payload value	Name	29-byte layout
`0x01`	Tx	`00 × 28 + 01`
`0x02`	Intermediate State Roots	`00 × 28 + 02`
`0x04`	PayForBlobs	`00 × 28 + 04`
`0x05`	PayForFibre	`00 × 28 + 05`
`0xff`	Primary Reserved Padding	`00 × 28 + ff`

A text character and a byte value are different: “ÿ” encodes to two UTF-8 bytes, not a single 0xff. Use decode mode to inspect raw reserved IDs.

Generation is not reservation

A namespace is a byte identifier, not a registered name. Generating one does not reserve it or give you exclusive ownership. Reserved protocol ranges are not application namespaces.

Activity belongs to a network

A live check reports Celenium's indexed records for the selected network at the time of the request. No records does not guarantee that the namespace is unused, including on other networks.