← previous blocknext block →recent activity
Analyzing
Block #87,703,684
16 transactions · 16 stateful · 2026-07-14 12:53:44 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,703,684 · 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
1w04w05w18w09w110w111w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee3b1b53…77dd
0xa6afd3…d132
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xfcad4d96…c690
0x34b655…2a6f
4 touches
1 conflict
0xfcad4d96…c691
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xacdf56b3…e33c
0xa6afd3…d132
4 touches
1 conflict
0xe84eac86…b89c
0xa6afd3…d132
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
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 0xee3b1b536b…3277dd
Audit this contract →
← previous block·next block →recent activity