← previous blocknext block →recent activity

Analyzing

Block #98,848,179

19 transactions · 18 stateful · 2026-08-24 20:02:49 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,848,179  ·  19 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

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x8140ae1d…5c08

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xd6bd849a…5597

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x065ff70b…356d

0x40c49f…2af0

4 touches
1 conflict

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

0x333b6df0…b6ff

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: MarginAccount

3 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity