Network reference

Constants worth keeping close if you're building anything that touches Dogecoin L1 directly.

Units

Explorer and every other API on this site return amounts in koinu unless a field name explicitly says otherwise (like sendDoge()'s amount, which is DOGE — see Sending). Always check the field name, not the magnitude, before assuming which unit you're holding.

Blocks & confirmations

Dogecoin targets roughly a one-minute block interval — noticeably faster than Bitcoin's ten minutes, which is part of why Dogecoin feels responsive for tipping and everyday payments. That speed is also why you shouldn't treat "one confirmation" as final for anything high-value: reorgs of a block or two are more common on any fast-block chain than on a slow one. Match your confirmation threshold to the value at risk rather than hard-coding a single number everywhere.

Fees

Dogecoin uses a fee-per-byte model, not a gas market — a transaction's cost scales with its size (number of inputs and outputs), not with any notion of computational complexity. DRC-20 sends cost more than a plain DOGE send because the commit and reveal transactions carry inscription data.

Where things live