← previous blocknext block →recent activity
Analyzing
Block #86,828,816
14 transactions · 9 stateful · 2026-07-10 11:23:28 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,828,816 · 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x079017cd…e5a7
0x34b655…2a6f
4 touches
1 conflict
0x2e36fd33…c7f1
0x34b655…2a6f
4 touches
1 conflict
0x833d2d11…e7ba
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2878
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2879
0x34b655…2a6f
4 touches
1 conflict
0xac1cfdbd…99fe
0x34b655…2a6f
3 touches
1 conflict
0x361cb4cb…4aae
0x34b655…2a6f
2 touches
0 conflicts
0x4f0a4e1f…30ae
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 0x079017cda4…d1e5a7
Audit this contract →
← previous block·next block →recent activity