← previous blocknext block →recent activity

Analyzing

Block #83,655,017

19 transactions · 16 stateful · 2026-06-25 18:33:22 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,655,017  ·  19 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

0xf86f15cd…38af

0x34b655…2a6f

8 touches
6 conflicts

0xda7f9bd2…e332

0x34b655…2a6f

6 touches
3 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x487922c6…dbd2

0x34b655…2a6f

6 touches
3 conflicts

0xc0b9bd73…7f1c

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 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

6 conflicts on slot 0xf86f15cdfb…b938af

← previous block·next block →recent activity