← previous blocknext block →recent activity

Analyzing

Block #82,730,042

26 transactions · 20 stateful · 2026-06-21 11:33:34 UTC

Parallelism

65/100

Blocked

60%

Avg conflicts / tx

1.31

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #82,730,042  ·  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

14 touches
21 conflicts

0x77d4ad2d…583c

0x34b655…2a6f

10 touches
10 conflicts

0x21e43e72…d2f6

0x34b655…2a6f

6 touches
3 conflicts

0x23a320fb…cbd7

0x34b655…2a6f

6 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x18c07e16…8d22

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

21 conflicts on slot 0x08913286f9…0ff0df

← previous block·next block →recent activity