← previous blocknext block →recent activity
Analyzing
Block #85,991,065
18 transactions · 16 stateful · 2026-07-06 14:04:53 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,991,065 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x293cb8e5…1eeb
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x451e945f…4fdc
0x065c9d…c394
3 touches
1 conflict
0xf9d54bd8…282a
0xd32edf…ff58
3 touches
1 conflict
0x57d5c3a3…9195
0x065c9d…c394
2 touches
0 conflicts
0x727dfab6…19b1
0x065c9d…c394
2 touches
0 conflicts
0xbe52f3dd…3fc9
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x293cb8e5d5…961eeb
Audit this contract →
← previous block·next block →recent activity