Junkcoin Network Hashrate
What is Junkcoin’s hashrate?
Hashrate is the total number of scrypt hash attempts pointed at Junkcoin each second, shown here in TH/s (terahashes per second, 10¹² hashes/s). Junkcoin targets one block every 60 seconds, so hashrate decides how the chain’s reward stream — a lottery stream, on this chain — is divided among the machines doing the work. Our node measured 767 TH/s as of 2026-10-09, a 7-day change of +2.1%.
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.
Whose hashrate is this, really?
Almost none of it is Junkcoin-only hardware. JKC has accepted AuxPoW since block 173,000 — the activation height sits in the node’s chainparams, under a strict single chain ID (0x2020) — and the scrypt work you see here was done for Litecoin. The number above is the slice of the Litecoin parent-pool basket pointed at JKC; 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 JKC-side miner economics, move this number. This chain has already lived the extreme version — at the November 2024 revival, the first 130,000 blocks landed inside three days as pool work piled on faster than daily retargets could answer. When a parent pool folds JKC into its merge roster — or drops it — this chain’s hashrate steps overnight while the machines themselves never changed. 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
headline estimate = total work over the last day ÷ elapsed seconds (the API recipe, from our own headers)
No one publishes a Junkcoin hashrate history series — the public explorers show a spot number and move on, and we would not quote one anyway. Our Junkcoin 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. The “Implied hashrate” tile applies the first formula to the live difficulty as a cross-check on the day average; on a chain that retargets only once every 1,440 blocks, the implied figure holds flat between epochs while the day average keeps moving, so the two legitimately diverge through most of each day.
Why it matters for miners
Your expected share of this chain’s reward stream equals your hashrate divided by network hashrate — and on Junkcoin “expected” is doing real work, because block rewards are a lottery with documented triple-reward and jackpot odds. You don’t point a rig at JKC directly: point a scrypt machine at a pool that carries it (ViaBTC, F2Pool, Binance Pool, EMCD or Mining-Dutch) and JKC arrives as a kicker on your LTC payouts, for hashes you were already doing. The Junkcoin Foundation publishes its own merge-mining tutorials aimed at home miners. In our first measured day of parent attribution (2026-10-02 to 2026-10-03), F2Pool tags sat on 88% of merged JKC blocks.
FAQ
- Why does Junkcoin’s hashrate move with Litecoin pools?
- Because the work is not JKC-side work. Junkcoin has been merge-mined (AuxPoW) under Litecoin parent pools since block 173,000: F2Pool (since 2024-12-09), ViaBTC (since 2024-12-16), Binance Pool (since 2024-12-23), EMCD and Mining-Dutch carry JKC in their LTC merge baskets, so the hashrate pointed at this chain is whatever slice of the Litecoin fleet those rosters aim at it. When a parent pool adds or drops JKC, this number moves — no JKC-side miner decided anything.
- What is merged mining (AuxPoW)?
- One round of hashing, two chains. A Litecoin miner embeds a commitment to a Junkcoin block in its LTC work; a solution good enough for Junkcoin’s difficulty counts on the Junkcoin chain via AuxPoW, at zero extra electricity. Junkcoin accepts this from block 173,000 under a strict single chain ID (0x2020). That carriage, not standalone JKC rigs, is where virtually all JKC blocks come from.
- Can JKC’s hashrate change when no miner touched JKC?
- Yes — and this chain is the case study. At the November 2024 revival, parent-pool work arrived so fast that the first 130,000 blocks were mined inside three days. A parent pool adding JKC to its merge roster, or dropping it, moves this chain’s hashrate overnight while every individual machine keeps doing exactly what it did yesterday. Basket add/drop decisions are precisely what the ribbon indicators on the JKC dashboard are reading.
- Where is the historical chart?
- No public Junkcoin hashrate history series exists — the explorers show a spot number and move on, keeping no history at all — and we do not draw charts from data we do not have. BasinTwo’s own node has archived every JKC block forward since 2026-10-02; the chart ships the day our archive serves the series.