← previous blocknext block →recent activity
Analyzing
Block #86,982,749
20 transactions · 19 stateful · 2026-07-11 04:32:21 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,982,749 · 20 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
1w05w06w18w09w013w114w115w216w018w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d1e78d…7877
0x40c49f…2af0
6 touches
3 conflicts
0x51d03c9d…57a7
0x34b655…2a6f
6 touches
3 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
6 touches
3 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x76d1e78d12…117877
Audit this contract →
← previous block·next block →recent activity