← previous blocknext block →recent activity
Analyzing
Block #83,651,930
20 transactions · 18 stateful · 2026-06-25 18:12:50 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,651,930 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w29w310w411w514w315w017w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac61d3a4…7da8
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0xf3c3669e…911a
0x34b655…2a6f
10 touches
10 conflicts
0x79e62da8…efdc
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
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
15 conflicts on slot 0xac61d3a497…e97da8
Audit this contract →
← previous block·next block →recent activity