← previous blocknext block →recent activity
Analyzing
Block #84,317,425
18 transactions · 15 stateful · 2026-06-28 20:08:28 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,317,425 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w19w210w112w213w015w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x610aa855…5ecd
0x34b655…2a6f
6 touches
3 conflicts
0x369a11e2…566f
0x34b655…2a6f
5 touches
3 conflicts
0x23c734b2…175d
0x34b655…2a6f
4 touches
1 conflict
0x29ed82c3…a80a
0x34b655…2a6f
4 touches
1 conflict
0x3a8b8f90…b8a9
0x34b655…2a6f
4 touches
1 conflict
0x3e505a15…70f8
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity