← previous blocknext block →recent activity

Analyzing

Block #83,636,706

20 transactions · 18 stateful · 2026-06-25 16:31:10 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,636,706  ·  20 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

0x369a11e2…566f

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x1bcbf4c9…d744

0x34b655…2a6f

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

8 touches
6 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

8 touches
6 conflicts

0xd58b9a66…1c23

0x34b655…2a6f

8 touches
6 conflicts

0xe8560632…4e78

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 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 0x369a11e278…dc566f

← previous block·next block →recent activity