← previous blocknext block →recent activity
Analyzing
Block #85,914,368
22 transactions · 14 stateful · 2026-07-06 05:33:05 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,914,368 · 22 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
1w02w18w09w111w212w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe96f8568…e97f
0x699abc…6a3b
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xd9f98026…ecec
0x699abc…6a3b
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity