← previous blocknext block →recent activity
Analyzing
Block #83,399,626
28 transactions · 27 stateful · 2026-06-24 14:08:46 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
2.11
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,399,626 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w18w29w310w411w512w613w316w423w524w625w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xdb13034e…be94
0x34b655…2a6f
10 touches
10 conflicts
0xb6632320…a3ce
0x34b655…2a6f
10 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0x967b4a40…7a78
0x34b655…2a6f
9 touches
12 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x124be23b…2cca
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity