← previous blocknext block →recent activity

Analyzing

Block #91,110,928

28 transactions · 24 stateful · 2026-07-28 16:56:01 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,110,928  ·  28 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2d651956…12e8

0x34b655…2a6f

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x28c714d9…9438

0xa6afd3…d132

4 touches
1 conflict

0xb566cc65…214d

0xa6afd3…d132

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

6 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity