← previous blocknext block →recent activity
Analyzing
Block #86,679,012
16 transactions · 16 stateful · 2026-07-09 18:42:42 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,679,012 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x459573ed…fbbe
0x34b655…2a6f
6 touches
3 conflicts
0x503b3a72…f6df
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x88bc5547…becb
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 0x459573ed17…94fbbe
Audit this contract →
← previous block·next block →recent activity