← previous blocknext block →recent activity
Analyzing
Block #86,281,041
16 transactions · 14 stateful · 2026-07-07 22:20:49 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,281,041 · 16 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
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xba83da08…56f9
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd75bf0cf…af6c
0x065c9d…c394
3 touches
1 conflict
0x04f7964e…cc09
0x065c9d…c394
3 touches
1 conflict
0x60b504a5…6802
0x065c9d…c394
2 touches
0 conflicts
0x6151f3e7…3a51
0x065c9d…c394
2 touches
0 conflicts
0xae3ffe20…b12b
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity