← previous blocknext block →recent activity
Analyzing
Block #91,087,634
25 transactions · 22 stateful · 2026-07-28 14:58:47 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,087,634 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w010w312w113w415w220w221w322w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
8 touches
6 conflicts
0xc6b1d981…1be2
0xa6afd3…d132
8 touches
6 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
6 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity