← previous blocknext block →recent activity
Analyzing
Block #83,617,676
44 transactions · 31 stateful · 2026-06-25 14:23:58 UTC
Parallelism
57/100
Blocked
77%
Avg conflicts / tx
2.23
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,617,676 · 44 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w28w310w011w112w013w114w215w316w417w518w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0x022f72c3…07b6
0xc8689a…ee79
16 touches
28 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
16 touches
28 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
16 touches
28 conflicts
0x8e4fdba3…18f1
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity