← previous blocknext block →recent activity

Analyzing

Block #82,272,008

26 transactions · 20 stateful · 2026-06-19 08:34:02 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.08

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #82,272,008  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x08913286…f0df

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa678cd56…4fab

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x25de453d…9573

0x34b655…2a6f

6 touches
3 conflicts

0x9365e097…ff56

0x34b655…2a6f

6 touches
3 conflicts

0xa67ee943…0936

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

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 0x08913286f9…0ff0df

← previous block·next block →recent activity