← previous blocknext block →recent activity
Analyzing
Block #89,703,655
20 transactions · 15 stateful · 2026-07-23 18:32:39 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,703,655 · 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
2w03w18w09w112w213w116w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0x744e66c4…d964
0xa6afd3…d132
5 touches
3 conflicts
0x68626649…03af
0xa6afd3…d132
5 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x177a0db3…545c
0x34b655…2a6f
4 touches
1 conflict
0x2078c8e9…8a21
0x34b655…2a6f
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity