← previous blocknext block →recent activity
Analyzing
Block #83,622,660
24 transactions · 20 stateful · 2026-06-25 14:57:19 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,622,660 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w311w412w514w015w617w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0xc2ab3ad1…a6bc
0x34b655…2a6f
4 touches
2 conflicts
0x5f3fc680…f989
0x34b655…2a6f
4 touches
1 conflict
0x62559200…afe1
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity