← previous blocknext block →recent activity
Analyzing
Block #83,626,768
92 transactions · 62 stateful · 2026-06-25 15:24:44 UTC
Parallelism
78/100
Blocked
76%
Avg conflicts / tx
3.23
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,626,768 · 92 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w28w09w110w211w318w319w433w372w273w374w475w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
40 touches
190 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
16 touches
28 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
16 touches
28 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
16 touches
28 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
12 touches
15 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
190 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity