← previous blocknext block →recent activity

Analyzing

Block #82,290,317

36 transactions · 23 stateful · 2026-06-19 10:36:10 UTC

Parallelism

69/100

Blocked

57%

Avg conflicts / tx

1.19

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #82,290,317  ·  36 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0x8c0a0eea…8d2d

0x34b655…2a6f

10 touches
10 conflicts

0xfcb9138a…3830

0xc8689a…ee79

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 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