← previous blocknext block →recent activity
Analyzing
Block #86,513,071
11 transactions · 10 stateful · 2026-07-09 00:10:54 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,513,071 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb13f77f8…2317
0x34b655…2a6f
8 touches
6 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
8 touches
6 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x87f3dc22…eb64
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 0xb13f77f89b…d32317
Audit this contract →
← previous block·next block →recent activity