← previous blocknext block →recent activity
Analyzing
Block #86,103,486
25 transactions · 23 stateful · 2026-07-07 02:35:17 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,103,486 · 25 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
1w02w13w26w07w19w210w013w315w116w221w022w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0xa19aba84…8922
0xa6afd3…d132
6 touches
3 conflicts
0x000b8cc9…7e3d
0xd32edf…ff58
5 touches
3 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7648af81…2af3
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity