← previous blocknext block →recent activity
Analyzing
Block #83,398,413
14 transactions · 9 stateful · 2026-06-24 14:00:38 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,398,413 · 14 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
5w06w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2ab3ad1…a6bc
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x3b8acfe4…a3d9
0x34b655…2a6f
4 touches
1 conflict
0x55445bb6…8db8
0x34b655…2a6f
4 touches
1 conflict
0x7bd465cf…18f2
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9c7571b3…9605
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 0xc2ab3ad132…8da6bc
Audit this contract →
← previous block·next block →recent activity