← previous blocknext block →recent activity
Analyzing
Block #86,620,473
11 transactions · 8 stateful · 2026-07-09 12:10:29 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,620,473 · 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
4w05w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00e6b7d4…52f6
0x34b655…2a6f
2 touches
0 conflicts
0x0416a14d…31ec
0x34b655…2a6f
2 touches
0 conflicts
0x0a7bbfd8…ebde
0x34b655…2a6f
2 touches
0 conflicts
0x3c6d5e0b…c50b
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity