← previous blocknext block →recent activity

Analyzing

Block #90,809,928

16 transactions · 15 stateful · 2026-07-27 15:40:46 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,809,928  ·  16 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

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0xe718c0a6…7693

0x34b655…2a6f

6 touches
3 conflicts

0x731e6d82…2883

0x065c9d…c394

4 touches
1 conflict

0xdf64e5e6…75e8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2886e2bc…6ab8

0x065c9d…c394

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

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

3 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity