← previous blocknext block →recent activity

Analyzing

Block #82,975,235

21 transactions · 18 stateful · 2026-06-22 14:51:42 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1.33

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,975,235  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x08913286…f0df

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x49d02518…ca01

0x34b655…2a6f

8 touches
6 conflicts

0x36a49c16…89b9

0xc8689a…ee79

6 touches
3 conflicts

0x2eb3373a…8aff

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x4c81502a…02ab

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

15 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity