← previous blocknext block →recent activity

Analyzing

Block #83,628,654

23 transactions · 18 stateful · 2026-06-25 15:37:22 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,628,654  ·  23 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

0x224bdb9c…ab41

0x34b655…2a6f

8 touches
6 conflicts

0xbb3504d4…b05f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x049cca71…b102

0x34b655…2a6f

6 touches
3 conflicts

0x5f3fc680…f989

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x75cdffd8…c217

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

6 conflicts on slot 0x224bdb9c4f…a6ab41

← previous block·next block →recent activity