← previous blocknext block →recent activity

Analyzing

Block #80,163,768

25 transactions · 22 stateful · 2026-06-09 14:20:23 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,163,768  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xc38151f2…2bcb

0xc8689a…ee79

4 touches
1 conflict

0x0a6f5e37…6c3c

0x34b655…2a6f

4 touches
1 conflict

0x81e1f4e8…08d7

0x34b655…2a6f

4 touches
1 conflict

0x85eb1316…bb9e

0x34b655…2a6f

4 touches
1 conflict

0x8fb0fecf…cb2f

0x34b655…2a6f

4 touches
1 conflict

0xa0f5612a…9804

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity