← previous blocknext block →recent activity
Analyzing
Block #86,929,167
15 transactions · 11 stateful · 2026-07-10 22:34:19 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,929,167 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w28w19w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x050376db…0f48
0x34b655…2a6f
4 touches
1 conflict
0x2ad76970…2bd8
0x34b655…2a6f
4 touches
1 conflict
0x4bd41fd9…4194
0x34b655…2a6f
4 touches
1 conflict
0x552ac70a…d74b
0x34b655…2a6f
4 touches
1 conflict
0x59ededb5…45c4
0x34b655…2a6f
4 touches
1 conflict
0x606bc50d…4c10
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity