← previous blocknext block →recent activity
Analyzing
Block #87,294,526
25 transactions · 21 stateful · 2026-07-12 15:16:50 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,294,526 · 25 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
1w04w05w17w08w29w113w014w115w116w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8b6e4c2…e20a
0x188d58…ea8e
6 touches
3 conflicts
0xe8b6e4c2…e20b
0x188d58…ea8e
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x033dddd2…ac15
0x34b655…2a6f
4 touches
1 conflict
0x1514ca4f…b95b
0x34b655…2a6f
4 touches
1 conflict
0x6ea1896c…e06f
0x34b655…2a6f
4 touches
1 conflict
0x6ea1896c…e070
0x34b655…2a6f
4 touches
1 conflict
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 0xe8b6e4c2d9…01e20a
Audit this contract →
← previous block·next block →recent activity