← previous blocknext block →recent activity
Analyzing
Block #86,772,135
17 transactions · 14 stateful · 2026-07-10 05:04:43 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,772,135 · 17 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
1w04w05w16w27w310w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x462c8be7…4f83
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0xbeedaa05…9eda
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf9944dae…d619
0xd32edf…ff58
3 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
2 touches
0 conflicts
0xcf17589f…048c
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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: 0xb1dbf05f…b1c0d3
1 conflict on slot 0x462c8be7ee…684f83
Audit this contract →
← previous block·next block →recent activity