Solo tracker attributes Bitcoin block 968,224 to NiceHash EasyMining
Source report: 2026-09-23 · Editorial analysis published: 2026-09-23
Bitcoin block 968,224 was confirmed on September 23 with a 3.14905148 BTC coinbase output. SoloBlocks attributes it to NiceHash EasyMining, while its hashrate and luck figures remain estimates.
Analysis and practical implications
This section is our analysis and illustrative calculations, separate from the source report.
What the blockchain confirms
Bitcoin block 968,224 has hash 0000000000000000000147345bea3208262b07e4de147ab3016cb57e8b24c7cd and a timestamp of September 23, 2026 at 04:48:07 UTC. Blockstream's public Esplora data confirms 3,500 transactions, a serialized size of 1,550,068 bytes, weight of 3,992,878 units, difficulty 132,757,073,449,487.52 and nonce 2,044,430,604. These fields are independently reproducible from the chain. They establish that a valid block was accepted; they do not by themselves reveal the purchaser of hashrate, electricity cost or financial result.
Reward and fee arithmetic
The coinbase transaction pays 314,905,148 satoshis, or 3.14905148 BTC, to one spendable output, plus a zero-value OP_RETURN output. Subtracting the 3.125 BTC subsidy for this halving era gives 0.02405148 BTC in transaction fees. Fees therefore represent about 0.764% of the total coinbase output. This calculation uses confirmed on-chain amounts and does not depend on the later dollar price. The receiving address proves control of the reward output only when it spends or signs; it does not disclose the beneficial owner, pool contract or costs incurred to obtain the winning share.
The attribution comes from a tracker
SoloBlocks labels the finder as NiceHash EasyMining and describes the event as a solo-mining result. Pool or service attribution generally relies on coinbase tags, payout patterns and observed service behavior rather than a mandatory identity field in the Bitcoin protocol. ASIC.tools therefore reports the attribution as the tracker's classification, not as a legal identification of an individual customer. The block record confirms the payout address and transaction data, but it cannot confirm who rented capacity, which machines produced the work or whether multiple counterparties participated behind the service.
Hashrate is an estimate, not a meter reading
The tracker shows an estimated miner hashrate of 4.03 EH/s derived from a window of 155 blocks. Any estimate based on block arrivals is noisy because mining is probabilistic: the same underlying capacity can find blocks close together or wait much longer than average. It is not equivalent to a utility meter, miner dashboard or accepted-share total. The displayed one-in-229 per-block odds and 146.3% luck are model outputs built from assumptions and the selected window. They should not be used as a confirmed purchase quantity, session duration or repeatable probability for another order.
A block win does not establish profit
Gross reward is only one side of the event. A profitability calculation would also require the price and duration of rented or owned hashrate, service fees, pool terms, rejected work, network latency, financing and the value of BTC when sold or retained. None of those costs is encoded in the block. Converting the reward to dollars using a later spot price creates a dated valuation, not realized profit. A solo strategy has a highly uneven outcome distribution: one success can dominate many unsuccessful attempts, so this block cannot show the average return of EasyMining or solo mining generally.
Use BTC and satoshis for the primary reward record, then attach any fiat conversion with its exchange, timestamp and price. This prevents a changing market quote from being mistaken for a change in the block itself and keeps later audits reproducible.
Why the transaction count needs context
The block contains 3,500 transactions, but count alone does not measure demand or fee efficiency. Bitcoin blocks are constrained by weight, and transactions vary greatly in witness data, input count and output count. The 3,992,878-unit weight is close to the four-million-unit limit, while the 0.02405148 BTC fee total reflects the transactions the template selected at that moment. To evaluate construction quality, researchers would need the available mempool, fee rates, exclusions and propagation conditions immediately before the block, not merely a final count.
Probability should be communicated over many independent trials, not as a promise attached to one winner. A hashrate estimate can be converted into an expected time only after choosing the network difficulty and assuming the rate stays constant, yet actual waiting time can be much shorter or longer. Service customers also may share infrastructure or buy time-limited packages whose economics differ from owning machines. To compare strategies, record total spending and all attempts, including those that found no block. Publishing only a success creates survivorship bias. The confirmed block is valuable evidence of the outcome, but a decision about future solo mining needs the full distribution of outcomes and costs.
How to verify the event yourself
Start with height 968,224 in two independent explorers and compare the block hash, timestamp, coinbase transaction, reward output, weight and transaction count. For pool attribution, inspect the coinbase script and compare multiple trackers, while clearly labeling inference. Preserve the exact UTC time because market price, mempool and network estimates change continuously. Do not trust a screenshot showing only a dollar number. The reproducible core is the block header and confirmed transaction data; provider identity, rented hashrate and economic result require separate evidence.
A block can be independently valid even when attribution is disputed. That is why the article links the tracker for classification and uses public chain data for numerical facts. Readers should preserve both sources and note when either service later revises labels or estimates.
The defensible conclusion
A valid block at height 968,224 paid 3.14905148 BTC, including 0.02405148 BTC in fees. SoloBlocks attributes the result to NiceHash EasyMining and publishes statistical estimates around the event. This is notable evidence that a solo-oriented service found a block on September 23, but it is not evidence that every customer has similar odds or that the winning attempt was profitable. Future analysis should separate immutable chain facts from tracker classifications and from economic assumptions. That distinction keeps an unusual mining result informative without turning it into a marketing promise.
The timestamp in a block header is supplied by the miner within consensus bounds, while median-time-past and explorer display time are related but distinct concepts. For ordinary reporting, the confirmed header time is useful, but researchers measuring propagation should use their own node logs. Likewise, the winning nonce is one field in the header search; it does not reveal how many hashes the finder tried before success. Avoid reconstructing a precise cost or machine count from the nonce alone.
Source: Bitcoin network / SoloBlocks ↗
Mining calculator ↗
