Reading your block contribution log.
The fastest path from "I have a GPU or ASIC" to "shares are landing" on the testnet demo. Five steps.
01 What the contribution log is
The stack keeps an on-chain-verifiable contribution log. Every block the pool finds is recorded with its block hash and the share attribution that produced the settlement for that block — so the chain of “who contributed what” is written down and can be checked against the chain itself.
This is the transparency feature of the pool. Because each entry carries the real block hash, a miner does not have to take the numbers on trust: they can hold the log up against the public chain and confirm the block was found and how the attribution fell. All of it is testnet · no monetary value — the log records testnet coin units, which are not money and carry no price.
02 Reading a log entry
Each entry in the log carries a consistent set of fields:
- Block height — the position of the block on the chain.
- Hash — the block’s unique hash, the value you cross-check against the explorer.
- Found-at — when the pool found the block (UTC).
- Attributed shares — how the work that found the block was attributed across miners.
- Status —
confirmedororphan.
A log line reads like this:
The attribution percentages decide how the block’s testnet coin units are shared out at settlement time — again, testnet units with no monetary value.
03 Cross-checking a hash against the explorer
To verify an entry, take the hash from the log and look it up in the block explorer at explorer.getcrypto.co.in. The explorer is reading the same chain the pool settled against, so a confirmed block in your log will appear there at the same height with the same hash.
If the height, hash and timing line up, the entry is genuine — the pool really did find that block. This is what “on-chain-verifiable” means in practice: the log is not a private claim, it is a pointer into a public ledger anyone can inspect.
04 Confirmed versus orphaned blocks
Not every block the pool finds stays on the chain. Occasionally two valid blocks are found at nearly the same height and the network keeps only one; the other becomes an orphan. The log records orphans honestly, marked with orphan status, so the picture is complete rather than flattering.
The important rule: orphaned blocks are not settled. An orphan never made it into the permanent chain, so no testnet coin units are attributed for it — only confirmed blocks lead to a settlement. You will see an orphan in the log for transparency, but it carries no attribution.