← previous blocknext block →recent activity
Analyzing
Block #86,540,192
10 transactions · 9 stateful · 2026-07-09 03:12:11 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,540,192 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98d58911…19f2
0x34b655…2a6f
4 touches
1 conflict
0x16b7ae5c…881f
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x65033350…9b21
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x8a35acfb…d1a5
0xb1dbf0…c0d3
3 touches
1 conflict
0x143dba04…1b98
0xb1dbf0…c0d3
3 touches
1 conflict
0xb138d087…4689
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
1 conflict on slot 0x98d589117f…0c19f2
Audit this contract →
← previous block·next block →recent activity