← previous blocknext block →recent activity

Analyzing

Block #83,635,951

19 transactions · 16 stateful · 2026-06-25 16:26:07 UTC

Parallelism

58/100

Blocked

56%

Avg conflicts / tx

1.21

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

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

0x672fd8ba…9e9e

0x34b655…2a6f

10 touches
10 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0xe732567d…b65d

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xaa7ee7…f0e4

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

6 touches
3 conflicts

0x8e52f021…fd21

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

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

10 conflicts on slot 0x672fd8ba57…cf9e9e

← previous block·next block →recent activity