← previous blocknext block →recent activity

Analyzing

Block #82,729,908

23 transactions · 19 stateful · 2026-06-21 11:32:40 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,729,908  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0x8388eab6…83ff

0x34b655…2a6f

4 touches
1 conflict

0x99137b93…c390

0x34b655…2a6f

4 touches
1 conflict

0xbc04d98e…a484

0x34b655…2a6f

4 touches
1 conflict

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity