Dingocoin Network Hashrate

What is Dingocoin's hashrate?

Hashrate is the total number of scrypt hash attempts pointed at Dingocoin each second, shown here in TH/s (terahashes per second, 10¹² hashes/s). Dingocoin targets one block every 60 seconds, so hashrate decides how the chain's reward stream — a flat 10,000 DINGO per block since block 600,000, verified against a live coinbase on our node — is divided among the machines doing the work.

The headline number is computed from our own node's headers: the total work the chain accumulated over the last day — the sum of difficulty × 2³² per block — divided by the elapsed seconds. That exact recipe ships inside the API response itself, next to the number. As of 2026-10-03 it read 2,134 TH/s, a 7-day change of +0.8% against the prior week.

Whose hashrate is this, really?

Almost none of it is Dingocoin-only hardware. DINGO is merge-mined under Litecoin parent pools, and unlike its siblings it answers to two AuxPoW chain IDs — 0x62, the value Dogecoin itself uses, and 0x32. The scrypt work you see here was done for Litecoin; Dingocoin accepts it as proof-of-work through AuxPoW. The number above is the slice of the Litecoin parent-pool basket pointed at DINGO — compare it against LTC's own hashrate to see how big that slice is.

The consequence is worth saying plainly: basket add/drop decisions, not DINGO-side miner economics, move this number. When ViaBTC and f2pool both folded DINGO into their LTC baskets within a single week of March 2025, whole fleets began counting toward this figure at once — no DINGO-side miner decided anything. That is exactly the caveat in the box above, and it is why ribbon signals on a cross read pool-roster behavior rather than miner capitulation in the Bitcoin sense.

How we measure it — and why we don't borrow numbers

Nobody else publishes a Dingocoin hashrate series — in five and a half years of chain life, no explorer feed ever kept one, and we would not quote one anyway. Our Dingocoin node is synced block-by-block from genesis over the coin's P2P network, no snapshots, no third-party feeds, and integrity seals ride every API response. On 2026-10-03 the two formulas disagreed on purpose: the implied figure from the live difficulty read 1,331 TH/s against the 2,134 TH/s day average. On a chain that retargets every block (DigiShield, Dogecoin-1.14 class), that gap is what a freshly-moved difficulty looks like — the same slow block pace that shows up as the +0.018 pressure reading on the difficulty page.

Why it matters for miners

Your expected share of this chain's reward stream equals your hashrate divided by network hashrate. But on a merge-mined chain you don't point a rig at DINGO directly — you point a scrypt machine at a pool that carries it (ViaBTC, F2Pool, EMCD or Mining-Dutch) and DINGO arrives as a kicker on your LTC payouts, for hashes you were already doing. Both majors folded DINGO into their LTC baskets in the same week of March 2025, and our own first day of attribution capture (1,169 blocks, 2026-10-02 to 2026-10-03) was dominated by F2Pool, ViaBTC and AntPool tags.

FAQ

Why does Dingocoin's hashrate move with Litecoin pools?

Because the work is not DINGO-side work. Dingocoin is merge-mined (AuxPoW) under Litecoin parent pools, so the hashrate pointed at this chain is whatever slice of the Litecoin fleet pool rosters aim at it. Both majors added DINGO in the same week of March 2025 — ViaBTC on 2025-03-06, f2pool on 2025-03-07 — and our own first day of attribution capture (1,169 blocks, 2026-10-02 to 2026-10-03) read F2Pool, ViaBTC and AntPool tags on nearly nine of every ten of them. When a parent pool adds or drops DINGO, this number moves — no DINGO-side miner decided anything.

What is merged mining (AuxPoW)?

One round of hashing, two chains. A Litecoin miner embeds a commitment to a Dingocoin block in its LTC work; a solution good enough for Dingocoin's difficulty counts on the Dingocoin chain via AuxPoW, at zero extra electricity. Dingocoin adds a twist of its own: it accepts two AuxPoW chain IDs (0x62 and 0x32), so attribution by chain ID alone can never say who mined it. That pool carriage, not standalone DINGO rigs, is where virtually all DINGO blocks come from.

Can DINGO's hashrate change when no miner touched DINGO?

Yes — this chain watched it happen inside one week. When ViaBTC opened its DINGO pool on 2025-03-06 and F2Pool folded DINGO into its LTC basket on 2025-03-07, whole fleets began counting toward this number without a single machine changing what it hashed — and a roster drop would move it out the same way. Basket add/drop decisions are precisely what the ribbon indicators on the DINGO dashboard are reading.

Where is the historical chart?

No public Dingocoin hashrate history series exists anywhere — the chain has run since April 2021 and nobody kept the series — and we do not draw charts from data we do not have. BasinTwo's own node has archived every DINGO block forward since 2026-10-02; the chart ships the day our archive serves the series.