← previous blocknext block →recent activity
Analyzing
Block #89,413,755
18 transactions · 18 stateful · 2026-07-22 11:31:59 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,413,755 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w09w011w112w213w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a004c59…980d
0x188d58…ea8e
4 touches
1 conflict
0x1a004c59…980f
0x188d58…ea8e
4 touches
1 conflict
0x36cd3056…b5d4
0x188d58…ea8e
4 touches
1 conflict
0x36cd3056…b5d6
0x188d58…ea8e
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x201d7cf1…f7f2
0x34b655…2a6f
4 touches
1 conflict
0x2d10243d…c6bb
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
1 conflict on slot 0x1a004c59c1…17980d
Audit this contract →
← previous block·next block →recent activity