← previous blocknext block →recent activity

Analyzing

Block #91,410,621

25 transactions · 22 stateful · 2026-07-29 18:05:02 UTC

Parallelism

68/100

Blocked

55%

Avg conflicts / tx

1.12

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,410,621  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0x28c714d9…9438

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xb566cc65…214d

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…0002

0x48cba2…b48b

8 touches
6 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

6 touches
3 conflicts

0x5778d110…d2e6

0xc8689a…ee79

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

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

15 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity