← previous blocknext block →recent activity

Analyzing

Block #91,119,315

19 transactions · 15 stateful · 2026-07-28 17:38:12 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,119,315  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd6bd849a…5597

0x2a68ba…90c5

6 touches
3 conflicts

0x10d80fee…dbda

0x2b46c0…1669

6 touches
3 conflicts

0x55012d1a…3907

0x2b46c0…1669

6 touches
3 conflicts

0xa987699f…eabe

0x2b46c0…1669

6 touches
3 conflicts

0xb5c4826d…bdd6

0x2b46c0…1669

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfb874a6c…caa0

0x34b655…2a6f

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

3 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity