← previous blocknext block →recent activity

Analyzing

Block #82,970,666

23 transactions · 20 stateful · 2026-06-22 14:21:08 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,970,666  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0x08913286…f0df

0x34b655…2a6f

8 touches
6 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0xfd4c0c17…0ee6

0x34b655…2a6f

6 touches
3 conflicts

0x36a49c16…89b9

0xc8689a…ee79

6 touches
3 conflicts

0x6b47245e…a342

0x34b655…2a6f

6 touches
3 conflicts

0xd45bf713…49a6

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity