← previous blocknext block →recent activity

Analyzing

Block #88,140,231

18 transactions · 17 stateful · 2026-07-16 13:33:56 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,140,231  ·  18 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc6b1d981…1be2

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xc782ec05…5bb2

0xa6afd3…d132

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3692e331…7b27

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9465204c…bf37

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

3 conflicts on slot 0xc6b1d98106…cc1be2

← previous block·next block →recent activity