← previous blocknext block →recent activity
Analyzing
Block #83,625,861
59 transactions · 40 stateful · 2026-06-25 15:18:40 UTC
Parallelism
64/100
Blocked
83%
Avg conflicts / tx
4.14
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,625,861 · 59 txs across 21 waves · depth 21
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
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w29w212w315w418w521w624w726w651w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
42 touches
210 conflicts
0xe02484a6…c32e
0xc8689a…ee79
24 touches
66 conflicts
0x37a276a3…673f
0x34b655…2a6f
24 touches
66 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
24 touches
66 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
24 touches
66 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 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
210 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity