← previous blocknext block →recent activity
Analyzing
Block #86,133,226
15 transactions · 15 stateful · 2026-07-07 05:53:53 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,133,226 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6f5e37…6c3c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0x78b57f59…61c4
0x34b655…2a6f
4 touches
1 conflict
0x23a79489…1a00
0x065c9d…c394
2 touches
0 conflicts
0x5e585b14…83f8
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0x0a6f5e3795…116c3c
Audit this contract →
← previous block·next block →recent activity