← previous blocknext block →recent activity
Analyzing
Block #86,835,696
15 transactions · 12 stateful · 2026-07-10 12:09:28 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,835,696 · 15 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
1w02w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x35f7d43e…9954
0xd32edf…ff58
3 touches
1 conflict
0x2c2bdbf9…cb2a
0x065c9d…c394
2 touches
0 conflicts
0x6be3cd60…a0a5
0x065c9d…c394
2 touches
0 conflicts
0x8a9ee377…f705
0x065c9d…c394
2 touches
0 conflicts
0xb928606c…2411
0x065c9d…c394
2 touches
0 conflicts
0xc8461821…98ab
0x065c9d…c394
2 touches
0 conflicts
0xe23537c4…6fd4
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity