A cautionary message posted on X on August 5 advised Bitcoin users against looking up their own wallet addresses on public block explorers. The alert contended that these explorers record visitors' IP addresses, provide that data to Chainalysis, and in turn, make it available to government agencies.

Public block explorers are tools that permit anyone to view blockchain records by entering a specific address or transaction identifier. As with most websites, a hosted explorer receives a user's connection details along with the specific page they are requesting. When that request contains a public blockchain address, the site's operator technically gains the ability to link an internet connection to a demonstrated interest in that address.

This activity generates a layer of off-chain metadata that surrounds a public on-chain record. The privacy implications of this metadata hinge on several factors: whether the operator connects an IP address to a specific query, the duration for which that record is kept, and the parties to whom it might be disclosed.

Divergent Privacy Policies Across Major Explorers

An examination of published policies from WalletExplorer, mempool.space, Blockchair, Etherscan, Blockchain.com, and OKLink reveals substantially different approaches to user data. WalletExplorer is openly identified as a Chainalysis website and transparently states that it shares visitor information within the company. In contrast, the policies of other explorers vary, ranging from short retention schedules for webserver logs to retention based on specific purposes.

These policies collectively reinforce a specific conclusion: while hosted explorers are capable of gathering connection and request metadata, the practices of linking, retaining, and disclosing this data differ significantly from one operator to another.

WalletExplorer's Connection to Chainalysis

WalletExplorer's privacy notice explicitly states that its servers automatically log the IP address of a user and the URL they requested, which could include a Wallet Name, Wallet ID, or Bitcoin address. The policy further clarifies that this information, combining blockchain data with visitor data, is shared with other business units inside Chainalysis, confirming a disclosed data flow within the parent corporation. The notice also indicates that service providers may access or process this data to carry out functions for Chainalysis.

The site’s legal disclosure terms cover compliance with law enforcement requests, court orders, and other legal proceedings. This provision creates a pathway for data disclosure under designated legal circumstances but does not specify a numerical limit for how long visitor logs are retained. This privacy notice, last updated on October 14, 2021, remains the service's active published statement as of August 2026.

In 2021, a CoinDesk report authenticated leaked documents which detailed how WalletExplorer's IP data, when linked with Bitcoin addresses, was used to generate leads for law enforcement investigations. This incident directly involved both WalletExplorer and Chainalysis.

How Other Block Explorers Handle Data

The privacy policies of other block explorers show key differences in how they manage the link between an IP address and a user's query, as well as their data retention timelines. For instance, a third-party hosting, analytics, or security provider that processes data for an explorer is in a different position, and a standard processor clause in a privacy policy does not by itself prove that lookup records are being sold.

• IP-to-Query Linkage: WalletExplorer expressly connects an IP address to the requested URL. Similarly, mempool.space states its nginx logs gather an IP along with the requests made to the site. Blockchair notes that a browser sends both an IP and the requested page. In contrast, Etherscan, Blockchain.com, and OKLink use broader language to describe relevant data categories, which leaves the precise relationship between a query and an IP address unstated. While these broader terms might permit the collection of various data types, they don't confirm how records are joined in practice, leaving the linkage undisclosed without offering a privacy guarantee.

• Data Retention: The explorers employ different clocks and definitions for data retention. Etherscan distinguishes between raw webserver logs, which are kept for a shorter period, and its wider personal data lifecycle, which includes a 24-month disposal schedule for inactive personal data. Blockchain.com and OKLink utilize purpose-based language, meaning the retention duration is undisclosed if a policy provides no specific number.

• Law Enforcement Disclosures: WalletExplorer, Etherscan, Blockchain.com, and OKLink all have provisions for disclosing data to authorities under specified legal conditions. Blockchain.com maintains a separate law-enforcement guide that outlines the protocol it expects authorities to use. Such clauses confirm the possibility of access via legal process but do not reveal how often such requests are made. The policies for mempool.space and Blockchair do not specify their procedures for handling law enforcement requests.

The Limits of Explorer Metadata

It is important to understand that an explorer request only establishes a narrow fact: that an internet connection showed interest in a public address at a specific moment. Proving the identity, motive, ownership, and control of private keys requires independent evidence, such as information obtained through subpoenas, device forensics, or direct admissions.

As Blockchain.com's law-enforcement guide points out, a public blockchain address or transaction ID is generally less likely to yield useful customer information compared to a Blockchain.com wallet identifier, email address, or exchange account details. Likewise, CryptoSlate's wallet address guide clarifies the distinction between a public address for receiving assets and the private credentials needed to control them.

The 2021 report on WalletExplorer demonstrates how query metadata can become a valuable investigative lead, especially when combined with other data. A search query signals interest from a particular connection, but attributing ownership requires further corroboration.

Ultimately, using any hosted public explorer can expose a visitor to the collection of off-chain metadata. The actual privacy risk depends on the operator's specific policies regarding IP-to-query linkage, data retention windows, access given to service providers, and terms for legal disclosure. These dimensions offer a solid framework for comparing explorers and understanding the privacy trade-offs involved in what appears to be a simple address search.