← previous blocknext block →recent activity
Analyzing
Block #85,129,899
30 transactions · 28 stateful · 2026-07-02 14:27:29 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,129,899 · 30 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
1w02w03w14w05w16w07w08w19w214w216w117w018w119w220w321w423w126w227w3
- 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
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x3c189193…b97d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa2cc62d4…69f6
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