← previous blocknext block →recent activity

Analyzing

Block #98,913,537

29 transactions · 19 stateful · 2026-08-25 01:31:37 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,913,537  ·  29 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

0x00000000…003d

0x851145…3f07

12 touches
15 conflicts

0x08d53462…97ef

0x2b46c0…1669

10 touches
10 conflicts

0x5a409e7f…09b6

0x2b46c0…1669

10 touches
10 conflicts

0x7a12283f…b18a

0x2b46c0…1669

10 touches
10 conflicts

0x8649e48f…941c

0xc8689a…ee79

10 touches
10 conflicts

0xf7640726…19a2

0x2a68ba…90c5

10 touches
10 conflicts

0x8b2c44b4…7e59

0x2b46c0…1669

10 touches
10 conflicts

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