SoloFury ⚡ Multi-Coin SHA-256 Solo Mining Pool | BCH BTC BC2 BCH2 XEC | 1% Fee

[SoloFury]

Live multi-chain block explorer for solo miners — BTC · BCH · BC2 · BCH2 · XEC (free + embeddable)

Disclosure: I run SoloFury, a non-custodial solo SHA-256 pool. I built this explorer as a free public tool and wanted to share it with the solo-mining community here.

What it is
A single block explorer covering all five SHA-256 chains we support, with the data solo miners actually care about — live from our own full nodes:

• Latest blocks per chain — height, time, coinbase address, reward, tx count, size
• Mempool-style strip with the pool tag that mined each recent block
• SoloFury wins — every block our solo miners have found, verified on-chain (clickable to the address)
• Pool distribution and block-interval charts
• Expected-next estimate (pool hashrate vs network) and pool-luck tracking
• Retarget / halving context — useful for BC2 and BCH2 where this is hard to find elsewhere

Why it might be useful
Most explorers are single-chain (and the smaller SHA-256 alts barely have one). This puts BTC, BCH, BC2, BCH2 and XEC side by side, and adds the solo-specific stuff — who mined what, odds context, retarget drift — that generic explorers skip.

Languages
Available in 10 languages (EN/IT/DE/ES/RU/ZH/FR/JA/KO/PT-BR).

Embeddable
You can drop it on your own site/forum/shop with one line of code — three layouts (full / compact / strip+wins), pick the coin, iframe or JS widget. Generator here: solofury.com/embed-explorer/

Links
Explorer: solofury.com/explorer/
BC2 view: solofury.com/explorer/?coin=bc2
BCH2 view: solofury.com/explorer/?coin=bch2

Feedback welcome — happy to add fields or chains people want. It's a tool for the community first.

[SoloFury]

Thanks for the advice. I'm still trying new things. Check out the site.
Good luck with your mining!

[SoloFury]

👻 New free tool: Ghost Miner — a zero-watt solo mining simulator with REAL odds

Just shipped a companion tool for solo miners: Ghost Miner.

You summon a virtual rig on BTC, BCH, BC2, BCH2 or XEC and it hunts real blocks at the live network difficulty — same math as a real solo setup, zero electricity.

Two modes:

• Time Warp — fast-forward through "ghost-years". Blocks pass at the chain's true cadence; you lose almost all of them (just like reality), halvings cut the reward, until your ghost finally wins one.
• Live Haunt — register a ghost and it tracks real blocks in real time. Every draw is provably fair: HMAC(seed, coin:height:block_hash:ghost_id), with the daily seed hash committed before the blocks and revealed after — so you can recompute and verify every result yourself.

Also: a "Hall of the Haunted" leaderboard, an embeddable widget, and 10 languages.

👉 https://solofury.com/ghost/

BCH2/BC2 have the most winnable odds if you want to actually see a ghost land a block. Feedback welcome — especially on the provably-fair verification flow.

[Nexus9090]

Hi Rolando,

Just wanted to share some feedback with you.

I've switched to using Duckduckgo's browser and found that it will not connect to your servers and reports with the error below:-



I can still access using other browsers, so it looks like a problem with DuckDuckGo's browser or something else?

[SoloFury]

TLS / encrypted stratum now live on SoloFury — all 5 coins, all 9 regions
Quick update for anyone who's asked about encrypted connections: SoloFury now supports TLS stratum (stratum+tls://) across every coin (BTC, BCH, BC2, BCH2, XEC) and all 9 regions.
Setup is simple — the TLS port is just the plain port with a "1" in front:
BTC   6060 -> 16060
BCH   7070 -> 17070
BC2   8080 -> 18080
BCH2  8585 -> 18585
XEC   9090 -> 19090
Same hostname as before, only the port and protocol change. Example for a US-East miner:

stratum+tls://us-bch.solofury.com:17070
We use a publicly-trusted Let's Encrypt certificate, so on Bitaxe/AxeOS (2.13+) there's nothing to paste — just enable the TLS toggle in pool settings and you're encrypted end-to-end. Your worker name and share traffic no longer travel in the clear.
There's also a TLS toggle on the setup wizard ( solofury.com/start/ ) that generates the exact config for your coin and region.
Still non-custodial solo, still 1% fee. Feedback welcome as always.

[SoloFury]

Hi Rolando,

Just wanted to share some feedback with you.

I've switched to using Duckduckgo's browser and found that it will not connect to your servers and reports with the error below:-



I can still access using other browsers, so it looks like a problem with DuckDuckGo's browser or something else?

Hi, thanks a lot for reporting this
The key detail is the error itself: ERR_QUIC_PROTOCOL_ERROR. QUIC is the transport behind HTTP/3, which our CDN (Cloudflare) serves over UDP on port 443. What's happening is that the DuckDuckGo browser opens an HTTP/3 connection, it fails for some reason, and the browser doesn't fall back cleanly to regular TCP — so you get a dead page. Other browsers either complete the QUIC handshake fine or fall back to HTTP/2 over TCP automatically, which is why they work for you.

So it's not the pool servers being down — it's specifically how that browser handles HTTP/3. A couple of things on your side that usually fix it:

1. In the DuckDuckGo browser, try disabling HTTP/3 / QUIC if it exposes the setting (some builds do under experimental/network flags).
2. It can also be a local firewall or router silently dropping UDP on port 443 (QUIC uses UDP, normal HTTPS uses TCP). If you're behind a corporate/strict firewall, that would explain why only the QUIC path breaks.
3. As a quick test: connecting through a VPN, or from a different network, will usually tell us instantly whether it's the browser or your network path.

On my end: mining itself is completely unaffected — your miners connect to the stratum endpoints directly (e.g. us-bch.solofury.com), which don't go through Cloudflare's HTTP/3 at all, so your hashrate and payouts are never touched by this. This only affects viewing the website dashboard in that specific browser.

If it turns out a lot of people hit this, I can look at adjusting the HTTP/3 settings on the CDN side — but I'd rather not disable a performance feature for everyone over one browser's quirk unless it's widespread. Let me know if the steps above sort it out, or if anyone else is seeing the same thing.

Thanks again for the heads-up.