DigiByte blocks solved

Read this first: SoloLuck has not found a Bitcoin block

SoloLuck has not found a Bitcoin block. Nothing on this page is about Bitcoin, and nothing on it makes a Bitcoin block more likely.

This page is about a different chain. SoloLuck also runs a DigiByte solo pool, and that pool has solved 6 blocks on DigiByte mainnet. All six were found by machines the pool operator runs. Those DigiByte blocks are evidence about one thing: what this pool's software does with a block reward when it wins one. They are not evidence that an outside miner has been paid, and they are not evidence about Bitcoin.

Why publish them: a 0% fee on a pool that has not found a Bitcoin block is a promise. On DigiByte, what the pool software does with a won block is written on a public chain, 6 times, for anyone to read.

The blocks

6 of these rows were read off the public DigiByte chain by hand and checked through two explorers we do not run, most recently on 2026-09-11. The fee column is filled in only for those rows, because a pool reporting on itself is not evidence — the point is that you can read the same coinbase we did.

Every row was mined by SoloLuck's DigiByte pool on the sha256d algorithm. Each checked block contained a single transaction, its coinbase, so there were no transaction fees and the reward is the block subsidy alone. A row showing the em dash is a block this pool solved that nobody has read back by hand yet; its explorer links resolve now.

What one spendable output means

A block reward is not sent anywhere. It is created by the first transaction in the block — the coinbase — which the pool builds before the block is mined. Whoever writes that transaction decides where the reward goes.

In each checked block the coinbase created one spendable output holding the whole reward. A pool taking a fee would need a second spendable output or a smaller first one. Neither appears.

That is the difference between a fee policy and a fee structure. "0% fee" written on a website is a policy, and a policy can change without notice. A coinbase with no fee output is a structure, already on a public chain.

Who was paid. The machines that found these blocks are run by the pool operator, so each reward went to the operator's own address. What the blocks demonstrate is the structure of the payout, not a payment to anyone else.

You will count two outputs, not one. The second is a zero-value OP_RETURN holding the segwit commitment that every modern block carries; its script starts 6a24aa21a9ed and it pays nobody. Only one output in each of these coinbases is spendable.

Whose block it is. The coinbase input of each block carries the pool's signature: decoded from hex, its scriptSig ends in ckpool and /sololuck.io/.

Check it yourself

Two public explorers we do not run. Take any height from the table above.

1. Turn the height into a block hash:
   https://chainz.cryptoid.info/dgb/api.dws?q=getblockhash&height=24176239
2. Open that hash on the second explorer and read the block:
   https://digiexplorer.info/api/block/<hash>
   Confirm tx_count is 1 — the coinbase is the only transaction.
3. Read the coinbase itself:
   https://digiexplorer.info/api/block/<hash>/txs
   Entry [0] is the coinbase. Its vout holds one spendable entry with the full value and one entry of type op_return worth zero; its vin[0].scriptsig, decoded from hex, ends in /sololuck.io/.

Both explorers are third-party services and either may change its API or go offline. Any DigiByte node answers the same question with getblock, because the data is on the chain rather than on this site.

What this does not prove

• Nothing about Bitcoin odds. DigiByte and Bitcoin are separate chains with separate difficulties. Solving DigiByte blocks does not make a Bitcoin block more likely, sooner, or different in any way.
• That an outside miner has been paid. All six were found by machines the pool operator runs. An outside miner's block would carry the same structure paying their own address, but these blocks do not show one.
• DigiByte is a far smaller target. DigiByte aims for a block every 15 seconds across five algorithms, so sha256d sees one roughly every 75 seconds, and its sha256d difficulty is a small fraction of Bitcoin's.
• What runs on the Bitcoin side today. These blocks show how this pool's coinbase construction behaved on DigiByte. /proof demonstrates the Bitcoin construction on a test network; until a Bitcoin block is solved that remains a demonstration rather than an on-chain fact.
• Uptime, latency or support. See /status/history for the operating record.

Right now Bitcoin's difficulty is about 273,592× DigiByte's sha256d difficulty. Both figures are live from our own nodes: a DigiByte block is a far smaller target than a Bitcoin block, which is why this pool has solved DigiByte blocks and has not found a Bitcoin block.