← previous blocknext block →recent activity
Analyzing
Block #87,061,056
14 transactions · 14 stateful · 2026-07-11 13:15:34 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,061,056 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w28w19w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcc5ae85…6ba2
0xa6afd3…d132
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xa0bc9ef1…59a0
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586c
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x17c44db3…8888
0xa6afd3…d132
4 touches
1 conflict
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
1 conflict on slot 0xbcc5ae852a…5f6ba2
Audit this contract →
← previous block·next block →recent activity