How often does CraftCoin 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.0 s as of 2026-10-03; the live tile above updates it every 60 seconds.

How many CRC blocks per day?

About 1,440 at the 60-second target — 86,400 seconds in a day divided by 60. The measured pace on 2026-10-03 worked out to roughly 1,417. The actual count wanders with block-time luck and with parent-pool basket 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 basket shifts: when Litecoin parent pools re-aim the work pointed at CRC, blocks run fast or slow until DigiShield catches up — this chain's own first day is the extreme case, 41,700 blocks in about 18 hours while difficulty climbed from its genesis minimum. 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 on this chain there is nothing to borrow — no explorer, no feed; the one explorer link in the wild was dead when we checked on 2026-10-03. Our own node records every block and every AuxPoW parent coinbase, which is the dataset a block table with honest pool names needs; the table ships from that archive. We say so rather than guess.

CraftCoin Blocks — Live Height & Interval

What the block height counts

On most chains the height doubles as a clock. CraftCoin's needs a footnote, and we like footnotes: the genesis block is stamped 2013-06-12, block 1 follows on 2024-12-03 — an eleven-and-a-half-year silence between the chain's first two blocks — and the relaunch's opening ~18 hours minted 41,700 blocks while DigiShield climbed to meet the arriving parent-pool work. So 1,113,141 blocks as of 2026-10-03 works out to about 2.1 years of target-pace heartbeats, compressed into the 22 months since the relaunch actually began. Every one of those numbers is read from our own node, verified block-by-block from genesis over P2P — never an explorer quote, because for this chain there is no explorer to quote.

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

The interval tile is the chain's pulse against its target — 61.0 s on 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 basket 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?

Because we will not borrow one, and there is nothing to borrow: no public CRC block-feed API exists anywhere — the single explorer link in the wild was unreachable when we checked — and our public endpoint serves aggregates today. The table worth shipping is the one our own archive is already building: our node stores every AuxPoW header, and the parent coinbase inside each one names the pool that did the work — F2Pool, LitecoinPool.org, Mining-Dutch and Binance Pool tags on recent blocks, read directly rather than guessed from chain IDs (which this family has made provably unreliable — Dingocoin accepts two chain IDs, Dogmcoin's rotates yearly). That table ships from our archive, not from a borrowed feed.

Why it matters for miners

Blocks per day times the per-block reward is the entire stream this chain shares out, and CRC's arithmetic is unusually legible: a flat, measured 2-CRC subsidy means about 2,880 CRC a day at target pace, divided among whoever the parent rosters point at it — coin-denominated arithmetic, not a revenue claim. And interval drift is the earliest own-node tell that basket work moved: a parent pool re-aiming its roster shows up here as fast or slow blocks, minutes before any third party would report anything — if any third party reported this chain at all. Our archive also catches CRC blocks under LitecoinPool.org, Mining-Dutch and Binance Pool parent tags — AntPool tags appear only back in the December 2024 launch window — so check those pools’ payout pages before counting on a CRC kicker.

FAQ

How often does CraftCoin 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.0 s as of 2026-10-03; the live tile above updates it every 60 seconds.
How many CRC blocks per day?: About 1,440 at the 60-second target — 86,400 seconds in a day divided by 60. The measured pace on 2026-10-03 worked out to roughly 1,417. The actual count wanders with block-time luck and with parent-pool basket 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 basket shifts: when Litecoin parent pools re-aim the work pointed at CRC, blocks run fast or slow until DigiShield catches up — this chain's own first day is the extreme case, 41,700 blocks in about 18 hours while difficulty climbed from its genesis minimum. 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 on this chain there is nothing to borrow — no explorer, no feed; the one explorer link in the wild was dead when we checked on 2026-10-03. Our own node records every block and every AuxPoW parent coinbase, which is the dataset a block table with honest pool names needs; the table ships from that archive. We say so rather than guess.