← previous blocknext block →recent activity
Analyzing
Block #86,768,279
29 transactions · 22 stateful · 2026-07-10 04:38:55 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.34
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,768,279 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w012w013w315w118w224w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x274ac476…27fa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1d
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1e
0x34b655…2a6f
4 touches
1 conflict
0x7a0f48fc…72ae
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity