← previous blocknext block →recent activity
Analyzing
Block #85,896,828
16 transactions · 12 stateful · 2026-07-06 03:36:14 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,896,828 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a995
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a997
0x188d58…ea8e
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7c2ca8dc…f3c9
0x34b655…2a6f
4 touches
1 conflict
0x205f895f…739e
0x699abc…6a3b
4 touches
1 conflict
0xb5c8e99c…5508
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0x4dd1db394e…28a994
Audit this contract →
← previous block·next block →recent activity