← previous blocknext block →recent activity
Analyzing
Block #86,239,811
25 transactions · 19 stateful · 2026-07-07 17:45:29 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,239,811 · 25 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
1w02w14w08w29w317w119w020w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x8b4e26e9…2d61
0xd32edf…ff58
3 touches
1 conflict
0x848ef5b3…7d71
0x065c9d…c394
3 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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity