← previous blocknext block →recent activity

Analyzing

Block #89,771,727

24 transactions · 21 stateful · 2026-07-24 00:16:23 UTC

Parallelism

71/100

Blocked

48%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,771,727  ·  24 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

0xf7640726…19a2

0x2a68ba…90c5

8 touches
6 conflicts

0x08d53462…97ef

0x2b46c0…1669

8 touches
6 conflicts

0x5a409e7f…09b6

0x2b46c0…1669

8 touches
6 conflicts

0x7a12283f…b18a

0x2b46c0…1669

8 touches
6 conflicts

0x915c095e…c1e5

0x2b46c0…1669

8 touches
6 conflicts

0xcfe06a18…b5b5

0x2b46c0…1669

8 touches
6 conflicts

0xd8fd2add…50fc

0x2b46c0…1669

8 touches
6 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