← previous blocknext block →recent activity
Analyzing
Block #89,849,355
10 transactions · 9 stateful · 2026-07-24 06:48:07 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,849,355 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e016
0x188d58…ea8e
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0x2f7a3f51…7ebf
0xa6afd3…d132
3 touches
1 conflict
0x6f3f06bc…f179
0xd32edf…ff58
3 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c6
0x1b6862…e19c
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Uniswap: PoolManager
1 conflict on slot 0x00f7e3b74f…eee016
Audit this contract →
← previous block·next block →recent activity