Bitcoin BLAKE2b · every pool

Still hashing on stratum.

A stratum hasher lets the pool write the block. A DATUM miner writes it on their own node. An address is listed here when a pool's own public data shows it on that pool's stratum endpoint. 9 pools publish enough to tell, and each row says what it rests on.

As of 2026-10-06 21:40 UTC. Fourteen days of coinbases are read, chain tip 975,921. 161 addresses confirmed on stratum, 191 suspected, 2 moved to their own node.

Check one address

Look up

Showing Lazarus only. Show every pool · Confirmed (18) · Suspected (0) · Nice list (2) · How each pool is read · JSON

Pools

Every pool with blocks in the last fourteen days, and every pool we have checked. Choose a pool to see only its addresses. A block with a gateway tag was built on a miner's node. One without may be the pool's stratum or a gateway that writes no tag, so nothing is classified from that column.

Confirmed on stratum (18)

Suspected (0)

Not proof. The pool does not say which protocol these addresses use, so a miner on their own node can be in this table.

No suspect on Lazarus.

Nice list (2)

Addresses we saw on stratum that the same source now shows on their own node. A miner who only ever ran a node is on neither list.

How each pool is read

B2Pool

Its block list says how each block was found (SV1, DATUM or RATUM), and each miner page lists the blocks that address found. Its DATUM label includes the pool's hosted gateway, where the pool still builds the block and the coinbase carries the pool's own tag, so a DATUM block counts as the miner's own only when the coinbase carries another gateway's tag. An address whose newest found block was built by the pool is confirmed. The rest of the split's payees are suspects, weighed by the pool's share of pool-built blocks.

PyBLOCK

The live window masks addresses. The snapshot committed with each found block lists every address with its stratum work, so the list is as of the pool's last block.

Lazarus

Live sessions from /api/miners and /api/gateways: each address is on stratum or on its own gateway.

Bitcoin Xor

The miner page shows a gateway tag beside an address that comes through a tagged gateway. An address with no tag is a suspect: an untagged gateway looks the same.

RIPTIDE

/api/contributors gives every address in the window with its SV1 work and its DATUM work.

PaperclipPool

/api/status gives every address in the window with its stratum work and its DATUM work.

Blockvase

/api/pool gives every address in the window with its public-stratum work and its DATUM work. The stratum port is closed, so stratum work there is what is left in the window.

CTRL

Not a pool on this chain any more: a stratum front. ctrlpool, formerly xbtpool. Its own DATUM pool found its last block at 974658. Since then its XBT stratum port (4333) sits in front of a gateway ctrlpool runs itself, pointed at another pool's DATUM window: its site says so and does not say whose. Since 2 October 2026 the server behind that port is connected to Lazarus as a gateway, so ctrlpool's hashers are paid by Lazarus's coinbase while ctrlpool's node builds their blocks. All five of its regional hosts hand out the same jobs, so that one gateway carries everything it has. It hides its miner list; the addresses listed are the ones seen behind that gateway.

dxpool

Its stratum pool is a separate product with account names and one coinbase output, so its hashers are not in the coinbase. The block list names each finder only in part. Any address can be checked against the stratum product one at a time; a hashrate there is confirmed.

CONVOY

The found-block list names the solver and whether the block came through DATUM. Only the finder of a non-DATUM block is confirmed; nothing separates the other payees.

Pow.re

A hashrate desk with no pool pages or API. Its blocks pay one or two outputs.

Mining-Dutch

Stratum only, with accounts and wallet payouts. Its API has pool totals and no addresses, so only the pool's own coinbase address can be listed.

AlphaPool

Its stratum pool stopped paying out alone at block 973964, but its public stratum ports (5555, 7333, 7777 on four hosts) still hand out work: they now sit in front of DATUM gateways the pool runs itself, so those blocks carry a gateway tag while the pool's node builds them. A block is tied to those ports by the job they handed out, which proves the gateway name is the pool's. Its API does not tie an address to a gateway, so the payees of those blocks are suspects, not confirmed. Proved so far, last 14 days: 124 of its 689 gateway blocks (18%) were built on gateways it runs itself, under the names Soggy Waffle, Grumpy Pickle, BlockBuster3000, Sweaty Beaver.

Omega Pool

DATUM only: its connect page says a miner pointed at the pool's port does not work. Most of its blocks carry no gateway tag because RATUM gateways do not write one.

Rabid Pool

DATUM only for this chain: its summary reports no stratum endpoint.

A pool not named here is listed in the table above as soon as it finds a block, marked not checked, and none of its payees are classified until its data has been read. Corrections: open an issue.