WalletExplorer

WalletExplorer’s distinctive feature is address grouping. If addresses appear together as inputs to one transaction, the site treats them as belonging to the same wallet; links through further transactions can expand that group. This is a tracing method, not proof of a person’s identity or ownership.

The search box accepts a Bitcoin address, transaction ID, service name or an extended public key such as XPUB, YPUB or ZPUB. Open a wallet result to inspect dated incoming and outgoing activity and the running balance. Show wallet addresses reveals the addresses in that inferred group. CSV Export can download the whole wallet history rather than only the visible page.

For your own investigation, use the pen icon to rename a wallet. Those names live in the browser’s local storage. The top-right menu can export, import or delete them; exporting is useful before changing browsers or clearing site data. Extended-public-key search also allows a shared name across the resulting wallets.

Treat the built-in service names cautiously. The site says its naming database has rarely been updated since 2016, so an old label is a lead to verify elsewhere. It also processes confirmed transactions only and normally runs one or two days behind the chain. It is poorly suited to deciding whether a payment made moments ago has arrived.

Public pages and exports do not require registration. Developers can use the public API without a key, including transaction, grouped-wallet and extended-public-key queries. Results have pagination controls, and callers need to handle possible rate-limit responses.