← previous blocknext block →recent activity
Analyzing
Block #86,929,046
30 transactions · 26 stateful · 2026-07-10 22:33:31 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,929,046 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w410w511w014w015w017w018w119w620w121w227w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xdc440c40…491f
0xd32edf…ff58
7 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x20375a54…6235
0x065c9d…c394
6 touches
3 conflicts
0x72b26880…e541
0x065c9d…c394
5 touches
3 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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0xce827910a4…82ff22
Audit this contract →
← previous block·next block →recent activity