← previous blocknext block →recent activity
Analyzing
Block #89,869,783
20 transactions · 16 stateful · 2026-07-24 08:30:52 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,869,783 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w012w013w114w218w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 conflicts
0x989252a1…d812
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
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-WETH/USDC
3 conflicts on slot 0x529e53cf07…5438e4
Audit this contract →
← previous block·next block →recent activity