← previous blocknext block →recent activity
Analyzing
Block #93,511,417
35 transactions · 30 stateful · 2026-08-06 02:14:59 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,511,417 · 35 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
1w04w15w06w17w28w310w011w013w117w218w019w120w222w023w127w428w232w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x890a1db9…1712
0xa6afd3…d132
10 touches
10 conflicts
0xa1ff0729…0146
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0x40970e69…da50
0x2b46c0…1669
8 touches
6 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 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 0x890a1db90d…dc1712
Audit this contract →
← previous block·next block →recent activity