← previous blocknext block →recent activity

Analyzing

Block #98,670,807

22 transactions · 17 stateful · 2026-08-24 05:05:30 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,670,807  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xe29352e4…eb37

0xa6afd3…d132

11 touches
15 conflicts

0x11b69a7e…334e

0xee8c0e…1242

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xdee1e659…9750

0x40c49f…2af0

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

21 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity