← previous blocknext block →recent activity

Analyzing

Block #99,089,106

18 transactions · 15 stateful · 2026-08-25 16:21:31 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,089,106  ·  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

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xb55f6c75…c2d2

0xa6afd3…d132

4 touches
1 conflict

0xded216ce…191a

0xa6afd3…d132

4 touches
1 conflict

0x5778d110…d2e6

0xc8689a…ee79

4 touches
1 conflict

0x9c6a9da2…c628

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0b3eb43a…ca08

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 0x0000000000…00003d

← previous block·next block →recent activity