← previous blocknext block →recent activity
Analyzing
Block #86,710,249
12 transactions · 10 stateful · 2026-07-09 22:11:07 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,710,249 · 12 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x5ba51e87…44ee
0xb1dbf0…c0d3
3 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x0e08f926…7d7b
0x40c49f…2af0
2 touches
0 conflicts
0x1493fb9a…5163
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 0x6c68ddc9e3…b0d106
Audit this contract →
← previous block·next block →recent activity