← previous blocknext block →recent activity
Analyzing
Block #83,632,130
28 transactions · 25 stateful · 2026-06-25 16:00:35 UTC
Parallelism
61/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,632,130 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w06w18w09w110w211w312w413w514w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
10 touches
10 conflicts
0x6ca8bab1…3957
0x34b655…2a6f
10 touches
10 conflicts
0x369a11e2…566f
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity