← previous blocknext block →recent activity

Analyzing

Block #80,501,408

22 transactions · 18 stateful · 2026-06-11 03:50:55 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,501,408  ·  22 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0x61e836b9…be49

0x065c9d…c394

4 touches
1 conflict

0xb6f1cccb…cf92

0x065c9d…c394

4 touches
1 conflict

0xce17e602…c172

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity