← previous blocknext block →recent activity

Analyzing

Block #82,965,790

25 transactions · 20 stateful · 2026-06-22 13:48:31 UTC

Parallelism

76/100

Blocked

45%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #82,965,790  ·  25 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

0x08913286…f0df

0x34b655…2a6f

12 touches
15 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x176cc2f5…6fad

0x34b655…2a6f

4 touches
1 conflict

0x1d6cb721…c88c

0x34b655…2a6f

4 touches
1 conflict

0x217bd767…b79e

0x34b655…2a6f

4 touches
1 conflict

0x379dc435…6616

0x34b655…2a6f

4 touches
1 conflict

0x4aaa45ec…7681

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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

15 conflicts on slot 0x08913286f9…0ff0df

← previous block·next block →recent activity