← previous blocknext block →recent activity
Analyzing
Block #88,040,375
23 transactions · 22 stateful · 2026-07-16 02:26:01 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,040,375 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w08w112w113w114w115w217w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x28c714d9…9438
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4f1ad4b4…e00a
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
1 conflict on slot 0xb566cc65b9…bf214d
Audit this contract →
← previous block·next block →recent activity