← previous blocknext block →recent activity
Analyzing
Block #86,315,338
10 transactions · 10 stateful · 2026-07-08 02:09:51 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,315,338 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x064e3a81…bd83
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x36b84ae5…4d03
0x065c9d…c394
3 touches
1 conflict
0x1e617ec8…4d62
0x065c9d…c394
2 touches
0 conflicts
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x40bb0d95…9292
0x065c9d…c394
2 touches
0 conflicts
0x8df118d3…32cc
0x065c9d…c394
2 touches
0 conflicts
0xc0bcdf35…94f7
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 0x064e3a8115…1ebd83
Audit this contract →
← previous block·next block →recent activity