← previous blocknext block →recent activity
Analyzing
Block #85,138,291
37 transactions · 28 stateful · 2026-07-02 15:23:31 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,138,291 · 37 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
1w03w06w07w110w011w116w017w118w019w120w027w228w329w230w431w434w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
8 touches
6 conflicts
0xc00f8ec2…f01b
0xd32edf…ff58
7 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x126a0344…4465
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
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
10 conflicts on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity