← previous blocknext block →recent activity

Analyzing

Block #80,309,520

19 transactions · 18 stateful · 2026-06-10 06:32:18 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,309,520  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xceba2b98…97b2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x90f07a4f…d932

0x34b655…2a6f

6 touches
3 conflicts

0x94710b77…a921

0x34b655…2a6f

6 touches
3 conflicts

0x2e4eea52…0c68

0xc8689a…ee79

6 touches
3 conflicts

0x7c6d3d6d…9deb

0x34b655…2a6f

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

0x69df8a…6292

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: Perpl

3 conflicts on slot 0xceba2b98d6…f097b2

← previous block·next block →recent activity