← previous blocknext block →recent activity

Analyzing

Block #83,659,541

26 transactions · 24 stateful · 2026-06-25 19:03:32 UTC

Parallelism

58/100

Blocked

54%

Avg conflicts / tx

2.38

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #83,659,541  ·  26 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x756ad195…36a3

0x34b655…2a6f

18 touches
36 conflicts

0xf324b405…ca30

0x34b655…2a6f

14 touches
21 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

14 touches
21 conflicts

0x022f72c3…07b6

0xc8689a…ee79

14 touches
21 conflicts

0x9b58e20f…2dd9

0x34b655…2a6f

14 touches
21 conflicts

0x329f2f7d…dcff

0x34b655…2a6f

12 touches
15 conflicts

0xd7fe05cd…207e

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

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

36 conflicts on slot 0x756ad19507…7536a3

← previous block·next block →recent activity