← previous blocknext block →recent activity

Analyzing

Block #80,275,042

25 transactions · 21 stateful · 2026-06-10 02:42:28 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #80,275,042  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb1

0x1b6862…e19c

6 touches
3 conflicts

0x9ac7a7cd…a059

0xd32edf…ff58

5 touches
3 conflicts

0x022b49db…a477

0x34b655…2a6f

4 touches
1 conflict

0x080ca4e8…d573

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity