← previous blocknext block →recent activity
Analyzing
Block #86,221,177
37 transactions · 32 stateful · 2026-07-07 15:41:04 UTC
Parallelism
81/100
Blocked
72%
Avg conflicts / tx
1.49
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,221,177 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w28w39w010w111w212w316w121w222w325w326w427w428w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xb56f0740…7542
0x34b655…2a6f
10 touches
10 conflicts
0xc7a15219…7745
0xa6afd3…d132
10 touches
10 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x7137a51c…871b
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity