← previous blocknext block →recent activity

Analyzing

Block #82,969,955

21 transactions · 16 stateful · 2026-06-22 14:16:22 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #82,969,955  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x21898044…a071

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x588da1c1…6ae5

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

0x34b655…2a6f

4 touches
1 conflict

0x6d94d7d6…6ed4

0x34b655…2a6f

4 touches
1 conflict

0x8672c4d6…675c

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

3 conflicts on slot 0x08913286f9…0ff0df

← previous block·next block →recent activity