← previous blocknext block →recent activity
Analyzing
Block #87,761,601
24 transactions · 23 stateful · 2026-07-14 19:21:21 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,761,601 · 24 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
1w02w13w26w012w013w115w016w117w318w419w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xf219f7cf…7379
0xa6afd3…d132
8 touches
6 conflicts
0x3464bbc5…a323
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xe2d8c9c0…d4d9
0xa6afd3…d132
4 touches
2 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x033dddd2…ac15
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d72
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity