← previous blocknext block →recent activity
Analyzing
Block #83,668,341
16 transactions · 15 stateful · 2026-06-25 20:02:13 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,668,341 · 16 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
1w02w14w07w08w19w210w312w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e1ce17e…98a7
0x34b655…2a6f
9 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x18f147b8…cfb4
0x34b655…2a6f
6 touches
3 conflicts
0x65df2980…8edc
0x34b655…2a6f
6 touches
3 conflicts
0xc1c98a49…76f1
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
10 conflicts on slot 0x4e1ce17e14…ed98a7
Audit this contract →
← previous block·next block →recent activity