← previous blocknext block →recent activity
Analyzing
Block #82,696,601
18 transactions · 17 stateful · 2026-06-21 07:50:20 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,696,601 · 18 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
3w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef37d75e…467b
0xe1c8b7…3022
16 touches
28 conflicts
0x12a9b76e…cb76
0x3bd359…433a
16 touches
28 conflicts
0x44ed742f…63f5
0x3bd359…433a
16 touches
28 conflicts
0x4eb758b8…b13b
0x3bd359…433a
16 touches
28 conflicts
0x74cc18cb…243e
0x9f3832…4ae4
16 touches
28 conflicts
0x74cc18cb…243f
0x9f3832…4ae4
16 touches
28 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
16 touches
28 conflicts
0xf8770132…e656
0x9f3832…4ae4
16 touches
28 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: 0xe1c8b733…e33022
28 conflicts on slot 0xef37d75e2d…2a467b
Audit this contract →
← previous block·next block →recent activity