← previous blocknext block →recent activity
Analyzing
Block #93,076,208
24 transactions · 21 stateful · 2026-08-04 13:46:03 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,076,208 · 24 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
2w03w14w25w36w48w09w111w012w513w114w216w017w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
8 touches
6 conflicts
0x1803586e…d149
0xa6afd3…d132
8 touches
6 conflicts
0x1a287886…0266
0xa6afd3…d132
8 touches
6 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity