DigiDollar transaction lookup
Paste a DigiByte mainnet transaction id. This page fetches the raw transaction from a public explorer and decodes the DigiDollar payload in your browser — the consensus type byte says what it is, the payload says what was created, and the raw bytes are shown so you can check every step yourself. Nothing is stored; nothing is sent anywhere except the explorer request.
DigiDollar amounts live in an OP_RETURN that begins DD. Its third byte is the consensus type: 1 mint, 2 transfer, 3 redeem. The payload always declares the DD outputs the transaction creates (the zero-value taproot outputs, in order). A redemption's field is therefore its change; what it burns is everything it consumed minus that. A redemption with no payload creates no DD output and burns everything it consumed. Amounts are integer cents.
Collateral is recognised when it is spent: the taproot control block carries the DigiDollar NUMS internal key (50929b74…803ac0), which the consensus code uses so collateral can only leave through the time-locked script path. At creation, a valued taproot output in a mint may be collateral or change — this page says so rather than guessing.
The explorer decodes DigiDollar too, and shows a DD address on each output. This page is an independent second implementation — it walks the consumed inputs to compute what a redemption actually burned, where the explorer displays the declared change as the "burn." When two decoders disagree, the raw bytes decide; our DD addresses are cross-checked against the explorer's and match.
Describes DigiByte Core v9.26.5 behaviour as of September 2026. Everything labelled Unverified is inferred rather than read from consensus data. Anything inferred wrong is our error — tell us. Decoder source: dd-decode.js (self-tested against every DigiDollar transaction of mainnet week one). Explorer data: digiexplorer.info.