← previous blocknext block →recent activity

Analyzing

Block #89,560,833

11 transactions · 9 stateful · 2026-07-23 03:54:30 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,560,833  ·  11 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

0xb566cc65…214d

0xa6afd3…d132

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x63a8652c…5b43

0x34b655…2a6f

4 touches
1 conflict

0x63a8652c…5b44

0x34b655…2a6f

4 touches
1 conflict

0x6474161a…6a37

0x34b655…2a6f

4 touches
1 conflict

0x8d59b150…7225

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810d

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810e

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

← previous block·next block →recent activity