← previous blocknext block →recent activity
Analyzing
Block #86,080,077
10 transactions · 9 stateful · 2026-07-06 23:59:07 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,080,077 · 10 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
1w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x239d6612…4a55
0x065c9d…c394
2 touches
0 conflicts
0x4bb34557…cbcd
0x065c9d…c394
2 touches
0 conflicts
0x4c2266c2…eff9
0x065c9d…c394
2 touches
0 conflicts
0xb9eb76d3…f80c
0x065c9d…c394
2 touches
0 conflicts
0xc565b6ec…42a6
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
3 conflicts on slot 0x95523e2aaf…734c01
Audit this contract →
← previous block·next block →recent activity