← previous blocknext block →recent activity
Analyzing
Block #82,968,786
18 transactions · 15 stateful · 2026-06-22 14:08:33 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,968,786 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w211w112w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f21840f…6cde
0x34b655…2a6f
12 touches
15 conflicts
0x36a49c16…89b9
0xc8689a…ee79
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x79dc5dae…a85e
0x34b655…2a6f
6 touches
3 conflicts
0xa163cff0…92b8
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xbd7e0241…07f5
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0x0f21840f7c…c86cde
Audit this contract →
← previous block·next block →recent activity