← previous blocknext block →recent activity
Analyzing
Block #83,624,777
73 transactions · 60 stateful · 2026-06-25 15:11:29 UTC
Parallelism
68/100
Blocked
77%
Avg conflicts / tx
5.12
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #83,624,777 · 73 txs across 23 waves · depth 23
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
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w110w212w315w418w519w620w721w822w923w1024w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
46 touches
253 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
22 touches
55 conflicts
0xd16ba145…d030
0x34b655…2a6f
20 touches
45 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
18 touches
36 conflicts
0xc2dcae88…f07a
0x34b655…2a6f
18 touches
36 conflicts
0xab981df1…2941
0x34b655…2a6f
18 touches
36 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0x0cdf9369…5331
0x34b655…2a6f
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
253 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity