← previous blocknext block →recent activity
Analyzing
Block #92,588,400
25 transactions · 19 stateful · 2026-08-02 20:50:10 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,588,400 · 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
2w03w14w211w012w113w215w216w317w319w422w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b1d981…1be2
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0xeba56708…8cd7
0x2b46c0…1669
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
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 0xc6b1d98106…cc1be2
Audit this contract →
← previous block·next block →recent activity