← previous blocknext block →recent activity
Analyzing
Block #83,668,264
54 transactions · 41 stateful · 2026-06-25 20:01:42 UTC
Parallelism
61/100
Blocked
78%
Avg conflicts / tx
3.33
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,668,264 · 54 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
1w02w13w24w05w17w29w010w111w212w313w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
14 touches
21 conflicts
0x2754e960…bcc1
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
12 touches
15 conflicts
0x65df2980…8edc
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
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
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity