← previous blocknext block →recent activity
Analyzing
Block #85,580,909
23 transactions · 18 stateful · 2026-07-04 16:31:10 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,580,909 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w29w010w212w115w217w319w320w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
4 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity