← previous blocknext block →recent activity

Analyzing

Block #98,729,001

28 transactions · 17 stateful · 2026-08-24 10:02:54 UTC

Parallelism

89/100

Blocked

35%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,729,001  ·  28 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

0x1a992fdd…6167

0xd32edf…ff58

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0001

0xfa32f9…f3f0

4 touches
1 conflict

0x8a2f9a36…fb4a

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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