← previous blocknext block →recent activity
Analyzing
Block #83,652,589
24 transactions · 24 stateful · 2026-06-25 18:17:14 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.83
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,652,589 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w08w19w210w311w412w513w614w717w318w419w821w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x705f195d…cc32
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
10 touches
10 conflicts
0xc34f7ec0…59cd
0x34b655…2a6f
8 touches
6 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity