← previous blocknext block →recent activity
Analyzing
Block #83,617,276
45 transactions · 35 stateful · 2026-06-25 14:21:18 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
3.18
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,617,276 · 45 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w212w013w114w215w316w017w118w219w320w421w522w623w724w825w926w1032w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
14 touches
21 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
12 touches
15 conflicts
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0x6e950d76…a10e
0xd32edf…ff58
9 touches
10 conflicts
0x708619a6…d52a
0x34b655…2a6f
8 touches
13 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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity