← previous blocknext block →recent activity

Analyzing

Block #97,899,352

20 transactions · 19 stateful · 2026-08-21 11:46:19 UTC

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,899,352  ·  20 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

0x5095cb33…2491

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xde5c131f…da2c

0xa6afd3…d132

6 touches
3 conflicts

0x4c20d376…0819

0x34b655…2a6f

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0x074c08f8…fb56

0x34b655…2a6f

4 touches
1 conflict

0x2528e717…2a22

0x34b655…2a6f

4 touches
1 conflict

0x6370f8a3…f016

0xa6afd3…d132

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 0x5095cb3362…c52491

← previous block·next block →recent activity