← previous blocknext block →recent activity

Analyzing

Block #97,730,834

15 transactions · 13 stateful · 2026-08-20 21:29:19 UTC

Parallelism

67/100

Blocked

62%

Avg conflicts / tx

1.13

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,730,834  ·  15 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

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x0adfec5f…8741

0xa6afd3…d132

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5d7b1d8b…3291

0xa6afd3…d132

6 touches
3 conflicts

0xf6c9bf9b…ac02

0x34b655…2a6f

6 touches
3 conflicts

0x280d1119…ee4d

0x34b655…2a6f

6 touches
3 conflicts

0xaa0273da…431b

0xa6afd3…d132

5 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity