← previous blocknext block →recent activity
Analyzing
Block #87,706,953
16 transactions · 14 stateful · 2026-07-14 13:15:38 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,706,953 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w18w09w111w112w013w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43fab434…896f
0xa6afd3…d132
4 touches
1 conflict
0xd580b132…ad31
0x065c9d…c394
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xe6a34ca2…4075
0x34b655…2a6f
4 touches
1 conflict
0x0ae0d84a…7213
0x065c9d…c394
3 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 0x43fab43468…d0896f
Audit this contract →
← previous block·next block →recent activity