Pepecoin Network Hashrate
What is Pepecoin's hashrate?
Hashrate is the total number of scrypt hash attempts pointed at Pepecoin each second, shown here in TH/s (terahashes per second, 10¹² hashes/s). Pepecoin targets one block every 60 seconds, so hashrate decides how the chain's fixed per-block reward stream is divided among the machines doing the work. Pepecoin is a meme coin; the numbers on this page are what we can measure about it.
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 Pepecoin-only hardware. PEP is merge-mined under Litecoin parent pools (AuxPoW chain ID 63): the scrypt work you see here was done for Litecoin, and Pepecoin accepts it as proof-of-work through AuxPoW. The number above is the slice of the Litecoin parent-pool basket pointed at PEP — 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 PEP-side miner economics, move this number. When a parent pool folds PEP 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)
Nobody else publishes a Pepecoin hashrate series — there is no explorer feed to quote, and we would not quote one anyway. Our Pepecoin 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 difficulty every block (DigiShield, Dogecoin-1.14 class), the two legitimately diverge for a while whenever difficulty has just moved.
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 PEP directly — you point a scrypt machine at a pool that carries it (ViaBTC, F2Pool, Binance Pool, EMCD, Kryptex or Mining-Dutch) and PEP arrives as a kicker on your LTC payouts, for hashes you were already doing. In most LTC merge rosters PEP is the default second kicker after BELLS.
FAQ
- Why does Pepecoin's hashrate move with Litecoin pools?
- Because the work is not PEP-side work. Pepecoin is merge-mined (AuxPoW) under Litecoin parent pools: pools like ViaBTC, F2Pool, Binance Pool, EMCD, Kryptex and Mining-Dutch carry PEP as a kicker 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 PEP, this number moves — no PEP-side miner decided anything.
- What is merged mining (AuxPoW)?
- One round of hashing, two chains. A Litecoin miner embeds a commitment to a Pepecoin block in its LTC work; a solution good enough for Pepecoin's difficulty counts on the Pepecoin chain via AuxPoW, at zero extra electricity. In most LTC merge rosters PEP is the default second kicker after BELLS. That carriage, not standalone PEP rigs, is where virtually all PEP blocks come from.
- Can PEP's hashrate change when no miner touched PEP?
- Yes — and that is the single most important thing to understand about this number. A parent pool adding PEP 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 PEP dashboard are reading.
- Where is the historical chart?
- No public Pepecoin hashrate history series exists anywhere, and we do not draw charts from data we do not have. BasinTwo's own node has archived every PEP block forward since 2026-10-02; the chart ships the day our archive serves the series.