App activity
A clearer view of what your app puts onchain.
Base Attribution OS
bc_vwmzy653A recorded proof sample. Counts describe these published operations only.
Snapshot- Operations in sample
- 1
1 transactions · 0 user ops
- Active wallets
- 1
Wallets with a successful operation
- Successful operations
- 100.0%
1 operations with a recorded status
- Recorded gas cost
- <0.000001ETH
1 operations with fee data
Activity over time
2 Jun – 1 Jul · UTC
Execution results
What happened onchain.
- Successful
- 1
- Reverted
- 0
- Status unavailable
- 0
At least two successful operations in this view. Wallets are addresses, not people.
Where activity goes
Recorded destination addresses.
Follow the attribution
Inspect the operations carrying your code, then check the paths that create them.
- Code decoded from calldata
- 1
- Code reported by the source
- 0
Lookup by code cannot reveal operations where the code is missing. Source audits check supported paths before release.
Operations
Open a transaction to inspect the onchain record.
| Transaction | Wallet | Time · UTC | Result | Gas · ETH |
|---|---|---|---|---|
0x657334…fe4926Transaction | 0xbb79e9…31fa64 | Successful | <0.000001 |
How to read these numbers
Periods use UTC dates and end at the source's observation time. Published samples can be historical. Operations without timestamps remain in the table and total, but are excluded from the daily chart.
Active wallets require a sender and a successful execution. ERC-4337 activity uses the UserOperation sender. A bundler transaction is not counted again when its operations are supplied.
Gas totals include only recorded fees. Ordinary transaction fees need both L1 and execution costs; UserOperations use their reported actual gas cost. They measure network costs, not app revenue.
These counts describe activity found with the selected code. They do not measure all app traffic, missing attribution, visits or marketing funnels. Imported and indexed rows are not independently RPC verified by this dashboard.