← previous blocknext block →recent activity
Analyzing
Block #85,578,802
11 transactions · 10 stateful · 2026-07-04 16:17:08 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,578,802 · 11 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
1w03w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x4466e8fc…ba5c
0x065c9d…c394
4 touches
1 conflict
0x33ce7179…56ad
0x065c9d…c394
3 touches
1 conflict
0x5dcd28a7…451d
0x065c9d…c394
3 touches
1 conflict
0x62e7afcb…8ce3
0x065c9d…c394
3 touches
1 conflict
0x6f2b6aea…6253
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
3 conflicts on slot 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity