← previous blocknext block →recent activity
Analyzing
Block #92,274,817
25 transactions · 19 stateful · 2026-08-01 18:33:05 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,274,817 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w310w011w413w516w017w118w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x40970e69…da50
0x2b46c0…1669
8 touches
6 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
8 touches
6 conflicts
0x1d44909b…e905
0xa6afd3…d132
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0x1d86f412…d0b5
0xa6afd3…d132
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity