← previous blocknext block →recent activity

Analyzing

Block #91,101,676

18 transactions · 17 stateful · 2026-07-28 16:09:28 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,101,676  ·  18 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0x21898044…a071

0x065c9d…c394

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xde95b18d…3751

0x34b655…2a6f

4 touches
1 conflict

0x7604a8f8…d63a

0x34b655…2a6f

4 touches
1 conflict

0x84ad80c8…6fa1

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: Market-MON/USDC

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity