← previous blocknext block →recent activity
Analyzing
Block #83,666,348
25 transactions · 21 stateful · 2026-06-25 19:48:53 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,666,348 · 25 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
6w07w111w212w313w416w519w620w221w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3464910…786f
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0xa09d7dd3…f843
0x34b655…2a6f
4 touches
1 conflict
0x0cdf9369…5331
0x34b655…2a6f
4 touches
1 conflict
0x3d4520be…b9c9
0x34b655…2a6f
4 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
10 conflicts on slot 0xc346491067…b0786f
Audit this contract →
← previous block·next block →recent activity