← previous blocknext block →recent activity
Analyzing
Block #91,160,632
17 transactions · 15 stateful · 2026-07-28 21:06:02 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,160,632 · 17 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
1w02w13w04w15w26w17w213w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
6 touches
3 conflicts
0xb566cc65…214d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x49e721de…b35a
0x34b655…2a6f
4 touches
1 conflict
0xba5ff1c3…4ff1
0x34b655…2a6f
4 touches
1 conflict
0xfd5be853…17a0
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