← previous blocknext block →recent activity
Analyzing
Block #83,629,410
24 transactions · 20 stateful · 2026-06-25 15:42:25 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,629,410 · 24 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
1w06w17w08w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x2cb897e4…21ea
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
10 touches
10 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
10 touches
10 conflicts
0x37582005…0ffe
0x34b655…2a6f
8 touches
6 conflicts
0x5ac91084…7c84
0x34b655…2a6f
8 touches
6 conflicts
0xaa8e438b…4e48
0xd32edf…ff58
3 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity