← previous blocknext block →recent activity
Analyzing
Block #86,624,761
26 transactions · 13 stateful · 2026-07-09 12:39:05 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,624,761 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x866bf367…7a60
0x188d58…ea8e
6 touches
3 conflicts
0x38aa1898…fdf5
0x1b6862…e19c
6 touches
3 conflicts
0x866bf367…7a62
0x188d58…ea8e
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8e8bad91…4e4b
0x1b6862…e19c
2 touches
0 conflicts
0x37547c92…05ef
0x3bd359…433a
2 touches
0 conflicts
0x8e8bad91…4e4b
0x3bd359…433a
2 touches
0 conflicts
0x02243fb1…3811
0x503d19…1d74
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
3 conflicts on slot 0x866bf367c5…d57a60
Audit this contract →
← previous block·next block →recent activity