← previous blocknext block →recent activity

Analyzing

Block #80,216,775

24 transactions · 19 stateful · 2026-06-09 20:13:59 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,216,775  ·  24 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

0x80afd9d9…57cf

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x39a45f01…2b79

0x34b655…2a6f

4 touches
1 conflict

0x5e0a8339…3fa2

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

← previous block·next block →recent activity