← previous blocknext block →recent activity
Analyzing
Block #86,708,969
14 transactions · 11 stateful · 2026-07-09 22:02:35 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,708,969 · 14 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
1w02w03w14w26w18w012w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x511ecf07…8ed0
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x43e7b0a2…eb95
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0xa8565401…c530
0x34b655…2a6f
6 touches
3 conflicts
0xcc21c22a…8ffc
0x34b655…2a6f
6 touches
3 conflicts
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 0x511ecf073e…d98ed0
Audit this contract →
← previous block·next block →recent activity