← previous blocknext block →recent activity
Analyzing
Block #89,669,532
17 transactions · 17 stateful · 2026-07-23 15:40:04 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,669,532 · 17 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
1w02w14w25w06w17w110w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75ce681…ba5f
0x188d58…ea8e
6 touches
3 conflicts
0xe75ce681…ba60
0x188d58…ea8e
6 touches
3 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
6 touches
3 conflicts
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xe75ce68176…09ba5f
Audit this contract →
← previous block·next block →recent activity