← previous blocknext block →recent activity

Analyzing

Block #97,826,469

21 transactions · 21 stateful · 2026-08-21 05:31:58 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,826,469  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x3cd6f7af…4a43

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3686cc89…4ffc

0xa6afd3…d132

6 touches
3 conflicts

0x40970e69…da50

0x2b46c0…1669

4 touches
1 conflict

0x7aa91b8f…d070

0x2b46c0…1669

4 touches
1 conflict

0x8cf3d245…1d0d

0x2b46c0…1669

4 touches
1 conflict

0x0f0ad60b…caf4

0x34b655…2a6f

4 touches
1 conflict

0x451e482b…7e7d

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 0x3cd6f7af99…874a43

← previous block·next block →recent activity