← previous blocknext block →recent activity
Analyzing
Block #90,535,128
11 transactions · 10 stateful · 2026-07-26 16:38:17 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,535,128 · 11 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
2w04w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
6 touches
3 conflicts
0x57b9e825…2d23
0xa6afd3…d132
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0xcf8fee95…3425
0xa6afd3…d132
3 touches
1 conflict
0xebd24894…80ef
0xa6afd3…d132
3 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
2 touches
0 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-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity