← previous blocknext block →recent activity
Analyzing
Block #86,810,215
14 transactions · 14 stateful · 2026-07-10 09:18:55 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,810,215 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf66a16ae…0da8
0x34b655…2a6f
4 touches
1 conflict
0xfab1627b…b819
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x273eabee…549e
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x31130c7e…0cc7
0x34b655…2a6f
4 touches
1 conflict
0x62db95d4…351c
0x34b655…2a6f
4 touches
1 conflict
0x6e3a3827…eac8
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
1 conflict on slot 0xf66a16ae36…390da8
Audit this contract →
← previous block·next block →recent activity