← previous blocknext block →recent activity
Analyzing
Block #86,384,915
6 transactions · 4 stateful · 2026-07-08 09:54:45 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,384,915 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x488d780b…c3b8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc6fe3f4…5714
0x065c9d…c394
3 touches
1 conflict
0x4aeb8c8b…5589
0x065c9d…c394
3 touches
1 conflict
0x1a32acf6…cabe
0x065c9d…c394
3 touches
1 conflict
0x4ec3eaa9…b8ad
0x065c9d…c394
2 touches
0 conflicts
0xbf2333df…6d83
0x065c9d…c394
2 touches
0 conflicts
0xc7e63567…2398
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 0x488d780b54…42c3b8
Audit this contract →
← previous block·next block →recent activity