← previous blocknext block →recent activity

Analyzing

Block #80,272,173

20 transactions · 18 stateful · 2026-06-10 02:23:20 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,272,173  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x3c791631…1e20

0x065c9d…c394

4 touches
1 conflict

0x7b7ef315…9da5

0x065c9d…c394

4 touches
1 conflict

0x80afd9d9…57cf

0x065c9d…c394

4 touches
1 conflict

0xc47533f0…3c1c

0x065c9d…c394

4 touches
1 conflict

0x1b5d2e60…99b5

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