TrumPOW Network Hashrate

What is TrumPOW’s hashrate?

Hashrate is the total number of scrypt hash attempts pointed at TrumPOW each second, shown here in TH/s (terahashes per second, 10¹² hashes/s). TrumPOW targets one block every 60 seconds, so hashrate decides how the per-block reward — 15,625 TRMP since the block-600,000 halving — is divided among the machines doing the work. TrumPOW is a political-meme coin; this page carries chain measurements, not commentary.

The headline figure 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, next to the number it produces. As of 2026-10-03 it read 687 TH/s, a seven-day change of -1.2%.

Whose hashrate is this, really?

Almost none of it is TRMP-only hardware. TrumPOW is merge-mined under Litecoin parent pools (AuxPoW chain ID 168, accepted from block 60,000): the scrypt work you see here was done for Litecoin, and TrumPOW accepts it as proof-of-work. The number above is the slice of the Litecoin parent-pool basket pointed at TRMP — compare it against LTC’s own hashrate to see how thin the slice runs.

On this chain the usual basket caveat sharpens into a single-roster caveat. Our node attributes TRMP blocks by the LTC parent coinbase tag in each AuxPoW header, and over the archive’s first day F2Pool signed 94% of 1,177 blocks. One pool’s merge-roster decision — add, drop, re-weight — can move most of this number overnight while every machine keeps hashing exactly as before. That is what the AuxPoW note above means, and it is why ribbon signals on this cross read roster behavior, not miner capitulation in the Bitcoin sense.

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

Nobody publishes a TrumPOW hashrate series we could borrow even if borrowing were allowed here: the chain’s mempool-fork frontend exposes a hashrate-history endpoint that returns empty, and its explorer shows only a spot figure. House rule regardless — nothing on this page is quoted from anyone. Our TrumPOW node is synced block-by-block from genesis over the coin’s P2P network, no snapshots, and integrity seals ride every API response. The “Implied hashrate” tile applies the headline formula to the live difficulty as a cross-check; on a chain that retargets 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 TRMP — you point a scrypt machine at a pool that carries it, and on TRMP that means F2Pool for all practical purposes — the one verified major payer; our attribution also catches Mining-Dutch and Binance Pool tags, but verify a pool’s payout terms before counting the kicker. TRMP then arrives as a kicker on LTC payouts, for hashes you were already doing — and since block 600,000, each block’s kicker is half what it was the week before. F2Pool is the one verified major payer — its parent coinbases signed 94% of the 1,177 TRMP blocks our node attributed over the archive’s first day, with Mining-Dutch and Binance Pool tags covering most of the rest.

FAQ

Why does TrumPOW’s hashrate move with Litecoin pools?

Because the work is not TRMP-side work. TrumPOW is merge-mined (AuxPoW) under Litecoin parent pools, and our measured attribution says the carriage is effectively one roster: F2Pool’s parent coinbases signed 94% of the 1,177 TRMP blocks our node attributed over 2026-10-02 to 2026-10-03, with Mining-Dutch, Binance Pool and a few small stratum operators covering the rest. The hashrate pointed at this chain is whatever slice of the Litecoin fleet those rosters aim at it — when one adds or drops TRMP, this number moves, and no TRMP-side miner decided anything.

What is merged mining (AuxPoW)?

One round of hashing, two chains. A Litecoin miner embeds a commitment to a TrumPOW block in its LTC work; a solution good enough for TrumPOW’s difficulty counts on the TrumPOW chain via AuxPoW, at zero extra electricity. TrumPOW has accepted AuxPoW since block 60,000 under chain ID 168. That carriage, not standalone TRMP rigs, is where virtually all TRMP blocks come from.

Can TRMP’s hashrate change when no miner touched TRMP?

Yes — and on this chain the effect is sharper than anywhere else we measure, because one pool signs roughly 19 of every 20 blocks. A single merge-roster decision at F2Pool would move most of this number overnight while every individual machine keeps doing exactly what it did yesterday. Roster decisions are precisely what the ribbon indicators on the TRMP dashboard are reading.

Where is the historical chart?

No usable public TRMP hashrate history series exists — the chain’s own mempool-fork explorer returns an empty series from its hashrate-history endpoint (checked 2026-10-03) — and we do not draw charts from data we do not have. BasinTwo’s own node has archived every TRMP block forward since 2026-10-02; the chart ships the day our archive serves the series.