← previous blocknext block →recent activity

Analyzing

Block #83,637,117

30 transactions · 21 stateful · 2026-06-25 16:33:55 UTC

Parallelism

73/100

Blocked

57%

Avg conflicts / tx

1.2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #83,637,117  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x9ac79c76…c4a9

0x34b655…2a6f

14 touches
21 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

12 touches
15 conflicts

0xdc8d4ee0…def3

0x34b655…2a6f

8 touches
6 conflicts

0x9fbabe09…8dd6

0x34b655…2a6f

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

8 touches
6 conflicts

0x23454dd5…47b5

0x34b655…2a6f

8 touches
6 conflicts

0x1018dbda…b4df

0x34b655…2a6f

8 touches
6 conflicts

0x022f72c3…07b6

0xc8689a…ee79

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

21 conflicts on slot 0x9ac79c76e2…88c4a9

← previous block·next block →recent activity