← previous blocknext block →recent activity
Analyzing
Block #86,618,336
20 transactions · 13 stateful · 2026-07-09 11:56:12 UTC
Parallelism
90/100
Blocked
15%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,618,336 · 20 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
1w03w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x83a2553a…ef0f
0xd32edf…ff58
3 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065d
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
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 0x46cb45de01…66a566
Audit this contract →
← previous block·next block →recent activity