← previous blocknext block →recent activity
Analyzing
Block #93,363,111
27 transactions · 22 stateful · 2026-08-05 13:49:22 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,363,111 · 27 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
1w02w13w26w07w19w010w011w113w116w317w218w319w020w421w423w024w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x1a287886…0266
0xa6afd3…d132
8 touches
6 conflicts
0x1803586e…d149
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xa67cccd7…836f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity