← previous blocknext block →recent activity
Analyzing
Block #85,012,178
32 transactions · 28 stateful · 2026-07-02 01:20:00 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,012,178 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w18w29w010w111w212w114w015w117w219w320w421w522w628w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x731e6d82…2883
0x065c9d…c394
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity