← previous blocknext block →recent activity

Analyzing

Block #84,427,450

23 transactions · 18 stateful · 2026-06-29 08:21:49 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,427,450  ·  23 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

0x00000000…00c9

0x34b655…2a6f

10 touches
10 conflicts

0x6f132c01…cdcc

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x71e4ffd1…9beb

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…641f

0x34b655…2a6f

8 touches
6 conflicts

0xc8d59e0f…cfe0

0x34b655…2a6f

8 touches
6 conflicts

0xf195ad96…e0c3

0x34b655…2a6f

8 touches
6 conflicts

0x130b8bf2…8fd7

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

10 conflicts on slot 0x0000000000…0000c9

← previous block·next block →recent activity