← previous blocknext block →recent activity
Analyzing
Block #86,678,224
20 transactions · 16 stateful · 2026-07-09 18:37:26 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,678,224 · 20 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
1w02w13w25w07w010w111w112w213w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x555491fd…ac54
0xd32edf…ff58
5 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7f2141d6…42bd
0x34b655…2a6f
4 touches
1 conflict
0x8fa1ba4f…a56f
0x34b655…2a6f
4 touches
1 conflict
0x8fa1ba4f…a570
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity