← previous blocknext block →recent activity

Analyzing

Block #80,822,977

26 transactions · 20 stateful · 2026-06-12 15:36:10 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #80,822,977  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xc38151f2…2bcb

0xc8689a…ee79

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xa51de3df…c65a

0x34b655…2a6f

4 touches
1 conflict

0xb6632320…a3ce

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity