← previous blocknext block →recent activity

Analyzing

Block #89,694,917

16 transactions · 15 stateful · 2026-07-23 17:48:41 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,694,917  ·  16 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc6b1d981…1be2

0xa6afd3…d132

8 touches
6 conflicts

0x529e53cf…38e4

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

6 touches
3 conflicts

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 0xc6b1d98106…cc1be2

← previous block·next block →recent activity