← previous blocknext block →recent activity
Analyzing
Block #83,629,413
26 transactions · 24 stateful · 2026-06-25 15:42:26 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,629,413 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w310w411w512w616w117w218w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5396d712…a139
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
14 touches
21 conflicts
0xcadc2eec…bbf5
0x34b655…2a6f
13 touches
21 conflicts
0x78a40728…8c95
0xd32edf…ff58
7 touches
6 conflicts
0xf98fe28b…4577
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 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 0x5396d712af…cba139
Audit this contract →
← previous block·next block →recent activity