← previous blocknext block →recent activity
Analyzing
Block #83,616,581
61 transactions · 50 stateful · 2026-06-25 14:16:39 UTC
Parallelism
67/100
Blocked
72%
Avg conflicts / tx
3.26
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,616,581 · 61 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
1w02w13w06w17w08w09w111w212w314w415w518w619w720w843w244w645w746w850w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0xc3464910…786f
0x34b655…2a6f
20 touches
45 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 conflicts
0x2484cc15…5afc
0x34b655…2a6f
16 touches
28 conflicts
0x5941ac48…c525
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
16 touches
28 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
14 touches
21 conflicts
0xdb067026…9eb8
0x69df8a…6292
14 touches
21 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