← previous blocknext block →recent activity

Analyzing

Block #82,969,100

24 transactions · 22 stateful · 2026-06-22 14:10:39 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.21

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #82,969,100  ·  24 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

0xea83a1f2…18ce

0x34b655…2a6f

10 touches
10 conflicts

0x08913286…f0df

0x34b655…2a6f

10 touches
10 conflicts

0xd45bf713…49a6

0x34b655…2a6f

10 touches
10 conflicts

0x718f636b…6023

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xbd7e0241…07f5

0x34b655…2a6f

6 touches
3 conflicts

0xd88f1b33…c285

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

10 conflicts on slot 0xea83a1f263…3818ce

← previous block·next block →recent activity