← previous blocknext block →recent activity

Analyzing

Block #82,965,687

22 transactions · 19 stateful · 2026-06-22 13:47:50 UTC

Parallelism

64/100

Blocked

58%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,965,687  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x06c59b8c…89c0

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x36a49c16…89b9

0xc8689a…ee79

8 touches
6 conflicts

0xf324b405…ca30

0x34b655…2a6f

8 touches
6 conflicts

0xfb859416…558c

0x34b655…2a6f

8 touches
6 conflicts

0x894c3474…190f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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