A higher ZEC price can improve Zcash mining revenue, but it does not automatically improve the return on a miner you buy today. Your share of the network, accepted work, electricity bill and delivery date all matter. The useful question is not simply “How much does a Z15 Pro earn?” It is “What remains if ZEC production falls before my machine starts operating?”
This guide separates coin production, operating margin and capital recovery. It includes a transparent stress test, not a live earnings quotation or a ZEC price forecast. Research was checked on November 4, 2026; every numerical scenario below is deliberately illustrative unless identified as a manufacturer specification.
Start with ZEC earned, not the dollar figure on a calculator
Record two separate quantities: the ZEC credited by your pool and the USD value assigned to it. Coin production can decline while its dollar value rises. Conversely, you might mine more ZEC but receive less cash after a price decline. Neither the miner's local hashrate screen nor a single estimated-profit screenshot establishes the amount you can withdraw and sell.
Zcash's own mining overview separates mining revenue, equipment investment and operating expenses. Use the same separation in your worksheet. First calculate the cash contribution from running the machine; then decide whether that contribution is sufficient to recover acquisition, installation and other capital costs. Positive cash flow is not the same as recovered capital.
For an existing machine, compare several complete daily settlement periods. Keep ZEC credits, pool deductions, accepted hashrate, uptime and wall-meter readings together. For a proposed purchase, use a time-stamped estimate and show how it changes under weaker conditions rather than extending today's number unchanged for a year.
Why difficulty can absorb a ZEC price increase
A simplified production model is:
Expected ZEC per day ≈ your effective share of network work × network blocks per day × the miner-attributable reward per block.
This is an expectation, not a promise of daily blocks. Pool reward methods, transaction fees, rejected shares and statistical variation affect settlement. Keep the reward credited to miners separate from total issuance. Avoid applying a second reward deduction if your data source already reports miner revenue.
Zcash's ZIP 208 specifies a 75-second post-Blossom target spacing. A target interval is not a guarantee that every block arrives on schedule. For a practical comparison at constant miner performance and reward rules, a rise in network competition reduces the share available to the same machine. Network hashrate and difficulty are related indicators: do not apply both as independent discounts to the same revenue estimate.
A simple sensitivity rule is new expected gross revenue / baseline gross revenue ≈ ZEC price multiplier / network competition multiplier. It holds only under the stated steady-state assumptions. A 20% price increase combined with 25% higher competition produces a revenue factor of 1.20 / 1.25 = 0.96, or roughly 4% less gross revenue. This relationship is arithmetic, not a claim that either movement will happen.
A Z15 Pro cost reference—with explicit limits
BITMAIN's Z15 Pro specification page lists 840 KSol/s and 2,780 W at the wall at 25°C for version 240-Z. The page describes these as typical values, with hashrate variation of ±3% and power variation of ±5%. Those figures are the reference used here, not measured results from a customer's miner.
At that reference power, continuous operation consumes 2.780 × 24 = 66.72 kWh per day. The following electricity costs exclude room ventilation, hosting services, taxes, repairs and financing. Use a meter and your actual tariff for an operating site.
| Electricity assumption | Reference consumption per day | Electricity cost per day |
|---|---|---|
| USD 0.06/kWh | 66.72 kWh | USD 4.00 |
| USD 0.08/kWh | 66.72 kWh | USD 5.34 |
| USD 0.10/kWh | 66.72 kWh | USD 6.67 |
| USD 0.12/kWh | 66.72 kWh | USD 8.01 |
The Z15 Pro 840K product page identifies the relevant configuration. Check its actual selected batch and condition before requesting an offer; a reference in this article is not an assertion of immediate stock. An 860K option is a different configuration and should not inherit the 840K inputs without verification. For physical differences and buying checks, see our Z15 versus Z15 Pro comparison.
Stress-test the margin before calling it a return
The table below starts from an invented USD 20.00/day gross revenue baseline, chosen only to demonstrate the method. It is not today's Z15 Pro revenue, a pool quotation or a market-price observation. Further assumptions are a hypothetical 2% pool fee, full-day operation, unchanged 2,780 W power, USD 0.08/kWh electricity, and unchanged reward rules. The competition factor represents an alternative network-work scenario after adjustment—not a second deduction on top of difficulty.
| Illustrative case | Price / competition multipliers | Gross revenue per day | After assumed pool fee and miner electricity |
|---|---|---|---|
| Baseline | 1.00 / 1.00 | USD 20.00 | USD 14.26 |
| Price rises; competition also rises | 1.20 / 1.25 | USD 19.20 | USD 13.48 |
| Price unchanged; competition rises | 1.00 / 1.50 | USD 13.33 | USD 7.73 |
| Price falls; competition rises | 0.70 / 1.50 | USD 9.33 | USD 3.81 |
Calculations use unrounded values and round the displayed result to two decimals. The last column is a limited operating contribution, not all-in net profit: gross revenue × 0.98 − 66.72 × 0.08. It excludes the other costs listed above and equipment depreciation. At these assumptions, the electricity-only gross-revenue break-even point is about USD 5.45/day. Your all-in threshold will be higher when additional expenses apply.
If your pool estimate already deducts its fee, do not deduct the fee again. Likewise, a hosting quotation that already includes electricity should not receive a second electricity charge. When comparing offers, put all amounts on the same cost basis before deciding which number is better.
A future batch earns nothing before it is running
For a future-delivery miner, split the worksheet into the waiting period and the operating period. The machine produces no mining revenue for you while it is awaiting delivery, customs clearance, installation or commissioning. A month label is not the same as a guaranteed start date at your site.
Recalculate the operating case using conditions at the expected start date, with a delayed-start downside case. Confirm the exact model, hashrate, condition, batch window, delivery terms and warranty start in the offer. Do not copy a current spot-unit earnings estimate into a future batch and treat the difference in equipment cost as pure extra profit.
Capital recovery is a separate calculation. If you use “upfront cost divided by daily cash contribution,” label it a static scenario and include relevant installation and transport costs. It is not a repayment schedule, especially where the daily contribution could change sign. Document site power, ventilation and commissioning checks before accepting an operating start-date assumption.
Check the path from pool balance to spendable funds
Revenue visibility is not identical to payment availability. As one pool-specific example, f2pool's Zcash guide describes Equihash ASIC mining, account-based worker naming and daily payouts after reaching its published 0.1 ZEC threshold. Confirm current account terms before relying on them; another pool may use a different threshold or settlement method.
Keep four records distinct: estimated production, settled pool credit, wallet receipt and any eventual conversion into USD. If you keep the ZEC instead of selling it, you still need funds to pay the electricity bill. Use an available executable sale quote, fees and actual settlement records when measuring realized cash, rather than treating a market ticker as a completed conversion.
For a deployment discussion, send LeedMiner the exact machine configuration, electricity rate or hosting cost basis, intended start date and an estimate with its source timestamp. We can help organize the hardware and deployment assumptions; the market outcome remains uncertain.
