← previous blocknext block →recent activity

Analyzing

Block #83,635,248

19 transactions · 16 stateful · 2026-06-25 16:21:25 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,635,248  ·  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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd5d0a749…c426

0x34b655…2a6f

8 touches
6 conflicts

0x842dd108…5fb0

0xd32edf…ff58

7 touches
6 conflicts

0xba7e9244…566e

0x34b655…2a6f

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x7322fb4a…635b

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity