← previous blocknext block →recent activity
Analyzing
Block #85,837,293
15 transactions · 13 stateful · 2026-07-05 20:59:38 UTC
Parallelism
53/100
Blocked
46%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,837,293 · 15 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
1w02w13w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0xbdf60a7e…c65a
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x6789fdc1…ff11
0x065c9d…c394
4 touches
1 conflict
0x9b55ff70…01a2
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity