← previous blocknext block →recent activity
Analyzing
Block #91,260,529
13 transactions · 12 stateful · 2026-07-29 05:28:40 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,260,529 · 13 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
1w02w03w14w16w07w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89678d1b…463e
0xa6afd3…d132
6 touches
3 conflicts
0xa1ff0729…0146
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x439cfb2c…7b9e
0xa6afd3…d132
4 touches
1 conflict
0xd27b62b1…9f49
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0xf9cae5f5…9c66
0xa6afd3…d132
3 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 0x89678d1b59…5a463e
Audit this contract →
← previous block·next block →recent activity