← previous blocknext block →recent activity

Analyzing

Block #98,644,230

19 transactions · 19 stateful · 2026-08-24 02:46:54 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,644,230  ·  19 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

0x9a369bdd…c46d

0xa6afd3…d132

10 touches
10 conflicts

0x11b69a7e…334e

0xee8c0e…1242

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x33600146…f67e

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b77

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

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

10 conflicts on slot 0x9a369bdd98…f8c46d

← previous block·next block →recent activity