← previous blocknext block →recent activity
Analyzing
Block #83,672,772
18 transactions · 13 stateful · 2026-06-25 20:31:43 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,672,772 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w011w212w313w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75cdffd8…c217
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x8873c4b6…4a47
0x34b655…2a6f
4 touches
1 conflict
0xbe5d230e…102f
0x34b655…2a6f
4 touches
1 conflict
0xd2862d04…388c
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xf607560e…828a
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 0x75cdffd8c9…dec217
Audit this contract →
← previous block·next block →recent activity