← previous blocknext block →recent activity
Analyzing
Block #86,612,434
50 transactions · 33 stateful · 2026-07-09 11:16:49 UTC
Parallelism
84/100
Blocked
58%
Avg conflicts / tx
0.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,612,434 · 50 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w315w218w119w320w024w325w426w427w028w136w540w641w443w747w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xfd55e4e7…0080
0xd32edf…ff58
7 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x391d170b…bd0f
0x3bd359…433a
6 touches
3 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
10 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity