← previous blocknext block →recent activity

Analyzing

Block #83,629,578

25 transactions · 23 stateful · 2026-06-25 15:43:32 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,629,578  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1222e42d…7dc8

0x34b655…2a6f

9 touches
10 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x82dd2252…e1ce

0x34b655…2a6f

8 touches
6 conflicts

0x5396d712…a139

0x34b655…2a6f

8 touches
6 conflicts

0xcbf6b053…cc04

0xd32edf…ff58

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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

10 conflicts on slot 0x1222e42dcb…377dc8

← previous block·next block →recent activity