← previous blocknext block →recent activity
Analyzing
Block #83,617,302
45 transactions · 34 stateful · 2026-06-25 14:21:28 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
1.93
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,617,302 · 45 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w19w211w413w314w415w518w019w120w221w322w423w524w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0x708619a6…d52a
0x34b655…2a6f
9 touches
10 conflicts
0xee532c30…4279
0xd32edf…ff58
9 touches
10 conflicts
0x23c5c9ed…69bb
0x34b655…2a6f
8 touches
6 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity