← previous blocknext block →recent activity
Analyzing
Block #86,389,098
10 transactions · 9 stateful · 2026-07-08 10:22:40 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,389,098 · 10 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3746c735…fb05
0x065c9d…c394
2 touches
0 conflicts
0x39125a06…67db
0x065c9d…c394
2 touches
0 conflicts
0x6269d609…9b3d
0x065c9d…c394
2 touches
0 conflicts
0xa55b37e5…4e36
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 0x27a04273d4…7327c5
Audit this contract →
← previous block·next block →recent activity