← previous blocknext block →recent activity

Analyzing

Block #80,787,803

28 transactions · 19 stateful · 2026-06-12 11:41:34 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,787,803  ·  28 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

0x217bd767…b79e

0x34b655…2a6f

8 touches
6 conflicts

0x679705f0…4531

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xce6ee9ac…fc82

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0x6b97d650…0509

0x34b655…2a6f

4 touches
1 conflict

0x7b6d2deb…dde0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

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 0x217bd767aa…4fb79e

← previous block·next block →recent activity