← previous blocknext block →recent activity
Analyzing
Block #86,911,349
21 transactions · 17 stateful · 2026-07-10 20:35:19 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,911,349 · 21 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
1w02w16w07w09w010w111w214w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3800d0ea…6168
0x34b655…2a6f
6 touches
3 conflicts
0x8cd0745d…4dc0
0x34b655…2a6f
6 touches
3 conflicts
0xba639250…76be
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0x3800d0eaaa…aa6168
Audit this contract →
← previous block·next block →recent activity