BOC decoder

A BOC is how TON serializes a tree of cells: messages, contract code and data. Paste one in base64 (te6cc…) or hex (b5ee9c72…) to see its header and cells.

Example: a jetton-transfer cell with a text comment

Result

Header

Format: standard · b5ee9c72
Size: 45 bytes, read as base64
Cells: 4
Roots: 1
Cell data: 34 bytes
Field sizes: 1 B per cell reference, 1 B per offset
Offset index: no
CRC32-C: none
Cache bits: no

Root 1 — cell #0 · hash 9e81f3beb70e912c91b96b5395b246f94e80ed6d353fffad0faf288a5e8f8296

Cells

#0 ordinary · 37 bits · 2 refs
hash 9e81f3beb70e912c91b96b5395b246f94e80ed6d353fffad0faf288a5e8f8296
x{0F8A7EA5AC_}
first 32 bits 0x0f8a7ea5 — matches the op-code of a jetton transfer (TEP-74)
#1 ordinary · 112 bits · 1 ref
hash 367e5c137daf5e819fd33b591f7262c72b3bbc8a1ab68f653392967135b47963
x{0000000068656C6C6F2C20746F6E}
first 32 bits 0x00000000 — matches the op-code of a text comment
text: hello, ton (continues in a reference)
#3 ordinary · 12 bits · 0 refs
hash c93cd577489ca23b8effc886e6b65a4c8c2da11891fa7ee6a86c40103d2ad185
x{ABC}
#2 ordinary · 1 bit · 1 ref
hash 47d47019b311ca32552d744f8de94ade1533ea1826c0babe3be669baddbea55a
x{C_}
#3 — shown above

Pure computation on apiton.org's server: nothing is read from the blockchain, and the result page is not cached. The input is part of the page address, so a result can be shared.

BOC decoder

Result

Header

Cells

Glossary

Other tools

Look up another name