← previous blocknext block →recent activity

Analyzing

Block #80,311,183

31 transactions · 22 stateful · 2026-06-10 06:43:25 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.45

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,311,183  ·  31 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x80afd9d9…57cf

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x21898044…a071

0x065c9d…c394

6 touches
3 conflicts

0x5dd3d853…5542

0xd32edf…ff58

5 touches
3 conflicts

0x0c93540d…6530

0x065c9d…c394

4 touches
2 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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 0x80afd9d9f2…3f57cf

← previous block·next block →recent activity