← previous blocknext block →recent activity

Analyzing

Block #83,623,130

22 transactions · 18 stateful · 2026-06-25 15:00:28 UTC

Parallelism

77/100

Blocked

44%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,623,130  ·  22 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

0xb4845723…8947

0x34b655…2a6f

10 touches
10 conflicts

0x022f72c3…07b6

0xc8689a…ee79

10 touches
10 conflicts

0xffc2f21e…b393

0x34b655…2a6f

10 touches
10 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0xe5f1db8a…41bb

0x34b655…2a6f

10 touches
10 conflicts

0x13aceb70…cf9f

0x34b655…2a6f

10 touches
10 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

10 touches
10 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

10 touches
10 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

10 conflicts on slot 0xb4845723a3…ed8947

← previous block·next block →recent activity