← previous blocknext block →recent activity
Analyzing
Block #82,229,739
11 transactions · 10 stateful · 2026-06-19 03:52:01 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,229,739 · 11 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0e44979…321f
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x924d6fe2…3caa
0x188d58…ea8e
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x791f4af9…3a78
0x34b655…2a6f
2 touches
0 conflicts
0x793aa64d…b09c
0x34b655…2a6f
2 touches
0 conflicts
0x793aa64d…b09d
0x34b655…2a6f
2 touches
0 conflicts
0x8a98d714…6ac1
0x34b655…2a6f
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 0xc0e44979c5…7b321f
Audit this contract →
← previous block·next block →recent activity