← previous blocknext block →recent activity
Analyzing
Block #86,819,656
13 transactions · 11 stateful · 2026-07-10 10:22:01 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,819,656 · 13 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
1w02w14w08w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc338dca8…8d5a
0xd32edf…ff58
3 touches
1 conflict
0x30313126…f27a
0x065c9d…c394
3 touches
1 conflict
0xb53a8bf4…85cd
0x065c9d…c394
3 touches
1 conflict
0x68c626fc…7a57
0x065c9d…c394
3 touches
1 conflict
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 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity