← previous blocknext block →recent activity
Analyzing
Block #85,913,430
14 transactions · 10 stateful · 2026-07-06 05:26:49 UTC
Parallelism
86/100
Blocked
10%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,913,430 · 14 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59691a7b…1c0e
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x06d3b3ea…2478
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x48aaf507…c755
0x065c9d…c394
2 touches
0 conflicts
0x1fdeff02…6d28
0x34b655…2a6f
2 touches
0 conflicts
0x1fe92c2a…cbb1
0x34b655…2a6f
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 0x59691a7b36…611c0e
Audit this contract →
← previous block·next block →recent activity