← previous blocknext block →recent activity
Analyzing
Block #86,822,817
37 transactions · 23 stateful · 2026-07-10 10:43:22 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,822,817 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w010w112w215w116w322w225w026w128w231w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
6 touches
3 conflicts
0x9367ddbf…cd91
0xd32edf…ff58
5 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8fa1ba4f…a56f
0x34b655…2a6f
4 touches
1 conflict
0x8fa1ba4f…a570
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
10 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity