← previous blocknext block →recent activity
Analyzing
Block #83,666,609
24 transactions · 21 stateful · 2026-06-25 19:50:38 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
0.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,666,609 · 24 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
1w02w14w05w18w29w310w411w512w618w719w222w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xcc2cd268…5687
0x34b655…2a6f
8 touches
6 conflicts
0x0cdf9369…5331
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6722ee42…ed53
0x34b655…2a6f
4 touches
1 conflict
0x7cdf7534…09e8
0x34b655…2a6f
4 touches
1 conflict
0x8d3f06db…98cb
0x34b655…2a6f
4 touches
1 conflict
0xe02484a6…c32e
0xc8689a…ee79
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity