Blockstream Explorer
Open-source explorer for Bitcoin and Liquid blockchains.
Open the official app on blockstream.info
This tool is hosted by its maintainers. Click below to open blockstream.info in a new tab — it's their official demo.
Browse network tools →What's next with Blockstream Explorer?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is Blockstream Explorer?
Blockstream Explorer is an open-source web tool designed to provide transparent, real-time access to Bitcoin and Liquid blockchain data. It serves as a block explorer, enabling users to query and visualize transaction details, block information, and address histories. The tool addresses the need for reliable, cache-ready data retrieval for developers and users interacting with blockchain networks. By leveraging the esplora-electrs HTTP API, it offers a lightweight interface for exploring blockchain activity. Blockstream Explorer is widely used by developers building decentralized applications, blockchain analysts, and end-users verifying transactions. Its primary purpose is to enhance trust and transparency by making blockchain data accessible and searchable, solving challenges related to data latency and complexity in blockchain networks.
How it works
Blockstream Explorer is a web-based interface for interacting with Bitcoin and Liquid blockchain data. It provides tools to search for transactions, blocks, and addresses, offering insights into network activity. The tool is built on the esplora-electrs HTTP API, which abstracts blockchain data retrieval. Its purpose is to deliver fast, reliable access to blockchain information for developers and users. It supports querying transaction details, block metadata, and address balances. Users can filter transactions by time, value, or sender/receiver. The interface also visualizes blockchain data through charts and tables, such as block sizes and fee rates.
How to use it
- 1Access the web interface via its public URL or self-hosted instance. 2. Use the search bar to query transactions, blocks, or addresses by hash or identifier. 3. Navigate through detailed views of individual transactions, including inputs, outputs, and fees. 4. Explore network statistics like block heights, confirmation times, and fee rates through dedicated dashboards. For API users, register for an API key to authenticate requests. Use endpoints like /api/v1/tx/{hash} to fetch transaction data programmatically. Combine with tools like Docker for local deployment.
What it can do
- blockchain explorer
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/Blockstream/esplora
- license: MIT — free to use
- privacy: Self-hosted — you control your data
Limitations
- Dependent on the electrs backend for data availability, which may have latency issues.
- Limited advanced analytics features compared to specialized blockchain tools.
- Requires technical expertise to self-host or integrate with custom systems.
- No built-in wallet functionality for sending or receiving funds.
- Public instance may have restricted access to certain data for privacy reasons.
Understanding the result
Open-source explorer for Bitcoin and Liquid blockchains.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (Blockstream/esplora)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with Blockstream/esplora. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- MIT License
Upstream project
Frequently asked
What is Blockstream Explorer used for?
Blockstream Explorer is used to query and visualize Bitcoin and Liquid blockchain data. It allows users to search for transactions, blocks, and addresses, providing transparency into network activity. Developers use it to integrate blockchain data into applications, while end-users verify transaction details and balances. It also supports QuickSync for faster node setup.
How does Blockstream Explorer retrieve blockchain data?
The tool uses the esplora-electrs HTTP API to fetch blockchain data. This backend service indexes Bitcoin and Liquid network data, enabling efficient querying. When a user searches for a transaction or block, the API retrieves pre-populated, cache-ready data from the indexed nodes, ensuring fast and reliable responses without requiring direct node interaction.
How do I use the Blockstream Explorer API?
To use the API, first register for an API key through the Blockstream Explorer dashboard. Once authenticated, send HTTP requests to endpoints like /api/v1/tx/{hash} to fetch transaction details. For example, to get information about a specific transaction, make a GET request with your API key as an authorization header. Refer to the API documentation for full endpoint details and rate limit guidelines.
How does Blockstream Explorer compare to alternatives like mempool.space or blockchain.com?
Blockstream Explorer focuses on Bitcoin and Liquid blockchain data with a lightweight, open-source interface. It integrates with the electrs backend for efficient data retrieval. In contrast, mempool.space emphasizes real-time mempool data and fee estimation, while blockchain.com offers a more user-friendly interface with additional tools like wallet services. Blockstream Explorer is ideal for developers needing customizable access, whereas blockchain.com caters to general users.
How do I troubleshoot a '404 Not Found' error when accessing a transaction?
A '404 Not Found' error typically indicates the transaction hash is invalid or the data is not indexed. Verify the transaction hash is correct by double-checking the source. If using the API, ensure the endpoint format is accurate (e.g., /api/v1/tx/{hash}). If the issue persists, confirm the electrs backend is operational and the node has synced fully. For public instances, some data may be restricted due to privacy settings.