← previous blocknext block →recent activity

Analyzing

Block #83,666,961

21 transactions · 21 stateful · 2026-06-25 19:53:00 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,666,961  ·  21 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

0xa0c6e179…a103

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x022f72c3…07b6

0xc8689a…ee79

8 touches
6 conflicts

0x1175233a…64e7

0x34b655…2a6f

8 touches
6 conflicts

0x2c53a187…3646

0x34b655…2a6f

8 touches
6 conflicts

0x5176765f…9af2

0x34b655…2a6f

8 touches
6 conflicts

0xdf37a93d…879b

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 0xa0c6e1796c…01a103

← previous block·next block →recent activity