← previous blocknext block →recent activity
Analyzing
Block #82,586,128
24 transactions · 20 stateful · 2026-06-20 19:30:20 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,586,128 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w07w09w110w111w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0xf9f48af5…4205
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca9295cf…d97c
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: Perpl
3 conflicts on slot 0x7be3246e43…72f89f
Audit this contract →
← previous block·next block →recent activity