Search Transaction ID
⌘V or double-click anywhere to paste
a user-friendly block explorer
Block explorers are the default surface for understanding what's happening on-chain. Over time, they have evolved into dense user interfaces that try to capture everything in a broad way, from transaction details, to chain analytics, to ecosystem apps.
Most users encounter explorers through transaction links, which usually serve as receipts. Apps provide them to verify a transaction went through, and users share them as proof. They want to confirm what happened, understand it, and be able to reference it. Developers, researchers, and data analysts have different needs. They rely on explorers to debug failed transactions, trace executions, validate contract deployments, and monitor how users interact with smart contracts.
Pulse separates these two experiences. The default view is minimal and opinionated, designed to cover the needs of most users, while Dev Mode provides a perspective closer to how existing explorers look.
Pulse is about breaking down the typical explorer experience and rebuilding it with intention and a user-first perspective.
Most users care about one thing when they land on an explorer: checking a specific transaction. The landing page is focused on exactly this. The search bar is auto-focused, so users can start typing immediately. Pasting anywhere on the page triggers the search. If the transaction hash is valid, they're taken directly to the transaction Receipt page. In the corner, blocks update in real-time to signal that the network is live.
The Receipt page is about capturing the essence of a transaction and presenting it in a way that's easy for the user to understand.
The default view focuses on token transfers, with values shown in dollars first, separated into payments (ERC-20) and assets (ERC-721). A generated human-readable summary describes what happened in the transaction. The View As bar lets users see the transaction from their own perspective, understanding inflows and outflows of payments and assets relative to their address. Dev Mode can be enabled on the Receipt page to get fully detailed insights into the transaction.
The Address page provides a quick overview of an address, focused on net worth in dollars and its holdings. Dev Mode can be enabled for a more detailed view.
Users can connect their wallet to see a personal dashboard. The view focuses on address's net worth and holdings denominated in dollars. The Activity tab shows a list of recent transactions the address has been involved in. Transactions are displayed from the user's perspective as inflows and outflows of tokens and assets relative to their address.
View Mode lets users switch between the default view and a detailed view (Dev Mode) on the Receipt and Address pages. It can be toggled using the Dev Mode button in the top right corner or via a query parameter in the URL (viewMode=dev), allowing shareable links that open directly in the intended view.
View As provides a personalized view at a transaction from a specific address's perspective. This includes indications for inflows and outflows, a more personalized summary, and labeling the viewing address as You to make it clear how the address is impacted by the transaction.
View As is enabled automatically when users sign in for their address (and can be disabled via profile settings) but can also be changed using the View As bar. It also syncs with a query parameter (viewAs=<address>), allowing apps and users to share links that open a transaction from a specific address's perspective.
Every transaction includes a human-readable summary so even non-technical users can understand what happened at a glance. When View As is enabled, the summary becomes more personalized describing the transaction from the viewing address's perspective.
You received $100.00 in USDC from 0x7465...6d706f
This might seem obvious, but defining what a payment is on-chain can be nuanced. A single transaction can contain multiple token transfers—some related to the actual payment, others related to fees or other types of value movement that aren't necessarily a payment in exchange for something. There's also the challenge of clarifying what was received in return for a payment and separating it from additional value that wasn't part of the exchange, like an airdrop or loyalty points for buying a product from the product itself.
Pulse uses heuristics to categorize transactions and determine the direction of value flow. The current logic works for simple cases but has room for improvement.
Direction detection
The logic counts the number of incoming vs. outgoing transfers relative to the viewing address. If more transfers are incoming, the transaction is labeled as received; if more are outgoing, it's sent. When counts are equal (common in swaps), it defaults to outgoing since the user initiated the transaction.
Category detection
The categorization of a transaction follows a priority chain:
Potential improvements
Search for an address or transaction
a user-friendly block explorer
Block explorers are the default surface for understanding what's happening on-chain. Over time, they have evolved into dense user interfaces that try to capture everything in a broad way, from transaction details, to chain analytics, to ecosystem apps.
Most users encounter explorers through transaction links, which usually serve as receipts. Apps provide them to verify a transaction went through, and users share them as proof. They want to confirm what happened, understand it, and be able to reference it. Developers, researchers, and data analysts have different needs. They rely on explorers to debug failed transactions, trace executions, validate contract deployments, and monitor how users interact with smart contracts.
Pulse separates these two experiences. The default view is minimal and opinionated, designed to cover the needs of most users, while Dev Mode provides a perspective closer to how existing explorers look.
Pulse is about breaking down the typical explorer experience and rebuilding it with intention and a user-first perspective.
Most users care about one thing when they land on an explorer: checking a specific transaction. The landing page is focused on exactly this. The search bar is auto-focused, so users can start typing immediately. Pasting anywhere on the page triggers the search. If the transaction hash is valid, they're taken directly to the transaction Receipt page. In the corner, blocks update in real-time to signal that the network is live.
The Receipt page is about capturing the essence of a transaction and presenting it in a way that's easy for the user to understand.
The default view focuses on token transfers, with values shown in dollars first, separated into payments (ERC-20) and assets (ERC-721). A generated human-readable summary describes what happened in the transaction. The View As bar lets users see the transaction from their own perspective, understanding inflows and outflows of payments and assets relative to their address. Dev Mode can be enabled on the Receipt page to get fully detailed insights into the transaction.
The Address page provides a quick overview of an address, focused on net worth in dollars and its holdings. Dev Mode can be enabled for a more detailed view.
Users can connect their wallet to see a personal dashboard. The view focuses on address's net worth and holdings denominated in dollars. The Activity tab shows a list of recent transactions the address has been involved in. Transactions are displayed from the user's perspective as inflows and outflows of tokens and assets relative to their address.
View Mode lets users switch between the default view and a detailed view (Dev Mode) on the Receipt and Address pages. It can be toggled using the Dev Mode button in the top right corner or via a query parameter in the URL (viewMode=dev), allowing shareable links that open directly in the intended view.
View As provides a personalized view at a transaction from a specific address's perspective. This includes indications for inflows and outflows, a more personalized summary, and labeling the viewing address as You to make it clear how the address is impacted by the transaction.
View As is enabled automatically when users sign in for their address (and can be disabled via profile settings) but can also be changed using the View As bar. It also syncs with a query parameter (viewAs=<address>), allowing apps and users to share links that open a transaction from a specific address's perspective.
Every transaction includes a human-readable summary so even non-technical users can understand what happened at a glance. When View As is enabled, the summary becomes more personalized describing the transaction from the viewing address's perspective.
You received $100.00 in USDC from 0x7465...6d706f
This might seem obvious, but defining what a payment is on-chain can be nuanced. A single transaction can contain multiple token transfers—some related to the actual payment, others related to fees or other types of value movement that aren't necessarily a payment in exchange for something. There's also the challenge of clarifying what was received in return for a payment and separating it from additional value that wasn't part of the exchange, like an airdrop or loyalty points for buying a product from the product itself.
Pulse uses heuristics to categorize transactions and determine the direction of value flow. The current logic works for simple cases but has room for improvement.
Direction detection
The logic counts the number of incoming vs. outgoing transfers relative to the viewing address. If more transfers are incoming, the transaction is labeled as received; if more are outgoing, it's sent. When counts are equal (common in swaps), it defaults to outgoing since the user initiated the transaction.
Category detection
The categorization of a transaction follows a priority chain:
Potential improvements