← previous blocknext block →recent activity

Analyzing

Block #80,574,476

20 transactions · 20 stateful · 2026-06-11 11:58:26 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,574,476  ·  20 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

0x070a562a…8147

0x34b655…2a6f

6 touches
3 conflicts

0xcfdb3285…de33

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0xc66627ac…6296

0xd32edf…ff58

5 touches
3 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0x75f928fc…0465

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 0x070a562acf…648147

← previous block·next block →recent activity