How often does TrumPOW find a block?

The target is one block every 60 seconds, and DigiShield re-aims difficulty at every block to hold that pace. Our own node measured the recent average at 61.4 s as of 2026-10-03; the live tile above updates it every 60 seconds.

How many TRMP blocks per day?

About 1,440 at the 60-second target — 86,400 seconds in a day divided by 60. The actual count wanders with block-time luck and with merge-roster shifts; the live tile computes the real figure from the measured interval.

Why is there no list of recent blocks here?

Because we will not borrow one, and our own public endpoint serves aggregates today. A third-party block feed exists for this chain, but we cannot verify it and will not quote it; and per-block pool names keyed on chain IDs would be guesses. Our node records every block and every AuxPoW parent header — the per-block table ships from that archive, pool attribution included, measured rather than guessed.

TrumPOW Blocks — Live Height & Interval

What the block height counts

One block is one 60-second heartbeat of the chain, so the height is a clock as much as a counter: 601,610 blocks as of 2026-10-03 works out to about 1.1 years of target-pace heartbeats, while the chain’s genesis — timestamped 2025-07-16 01:14 UTC on our node — sits closer to 14½ months back. The gap is the honest reading: real blocks never run exactly on target, and this chain’s lifetime average interval works out near 63.8 seconds. What makes our figure different from an explorer’s: this tip is verified block-by-block by our own node from genesis, over the coin’s P2P network. Nothing on this page is quoted from anyone.

The 60-second target, and what the interval tells you

The interval tile is the chain’s pulse against its target — 61.4 s on the recent average as of 2026-10-03. Averaging above 60 seconds means the work currently pointed at the chain is under-delivering against the difficulty it faces — and DigiShield answers within a block, easing difficulty until pace recovers. Averaging below means the opposite: extra work arrived and difficulty is climbing to meet it. The signed version of this story is the e_hafeer gauge on the difficulty page, recipe included.

One caveat we keep making because it keeps being true: luck dominates short samples. Block discovery is memoryless, so individual gaps scatter from seconds to many minutes on a perfectly healthy chain. Read the average, not the gap.

Where’s the block table?

We will not borrow one — not even from the chain’s own mempool-fork frontend, whose feed we have no way to verify and whose history endpoints come back empty (checked 2026-10-03). And borrowed rows would carry guessed pool names: AuxPoW chain IDs are unreliable attribution keys in this family — Dingocoin accepts two, Dogmcoin’s rotates yearly. Our node does it the hard way instead, reading the LTC parent coinbase tag inside every AuxPoW header, and the first measured day already attributed 1,177 TRMP blocks — 94% of them to F2Pool. The table worth shipping builds from that archive, and it will be the only one of its kind.

Why it matters for miners

Blocks per day times the per-block reward (subsidy plus fees) is the entire revenue stream this chain shares out — and the subsidy side of that stream just halved: block 600,000, crossed in the week of 2026-10-02, stepped the reward to 15,625 TRMP as of 2026-10-03. Interval drift is also the earliest own-node tell that roster work moved: a parent pool re-aiming shows up here as fast or slow blocks minutes before any third party reports anything — and on a chain where one pool signs 94% of blocks, that tell is worth watching. 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

How often does TrumPOW find a block?: The target is one block every 60 seconds, and DigiShield re-aims difficulty at every block to hold that pace. Our own node measured the recent average at 61.4 s as of 2026-10-03; the live tile above updates it every 60 seconds.
How many TRMP blocks per day?: About 1,440 at the 60-second target — 86,400 seconds in a day divided by 60. The actual count wanders with block-time luck and with merge-roster shifts; the live tile computes the real figure from the measured interval.
Why do intervals average above or below 60 seconds?: Two reasons. Randomness: block discovery is a lottery, so short samples scatter widely around the target even on a perfectly healthy chain. And roster shifts: TRMP’s carriage is concentrated — F2Pool signed 94% of the blocks our node attributed over the archive’s first day — so when that roster re-weights, the work pointed at this chain steps suddenly, and blocks run fast or slow until DigiShield catches up. Persistent deviation is exactly what the difficulty-pressure gauge reads.
Why is there no list of recent blocks here?: Because we will not borrow one, and our own public endpoint serves aggregates today. A third-party block feed exists for this chain, but we cannot verify it and will not quote it; and per-block pool names keyed on chain IDs would be guesses. Our node records every block and every AuxPoW parent header — the per-block table ships from that archive, pool attribution included, measured rather than guessed.