← previous blocknext block →recent activity

Analyzing

Block #84,335,732

22 transactions · 19 stateful · 2026-06-28 22:10:29 UTC

Parallelism

77/100

Blocked

37%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,335,732  ·  22 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

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0x7dc64b2c…05e7

0x34b655…2a6f

6 touches
3 conflicts

0x7e17e82a…9748

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe732567d…b65d

0x34b655…2a6f

6 touches
3 conflicts

0xf7468e81…86e5

0x34b655…2a6f

6 touches
3 conflicts

0x0c119c6d…a42e

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

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

6 conflicts on slot 0xffc2f21efe…ecb393

← previous block·next block →recent activity