← previous blocknext block →recent activity

Analyzing

Block #84,073,572

26 transactions · 23 stateful · 2026-06-27 17:04:08 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,073,572  ·  26 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

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0xf67a8937…7dbd

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x91220b8f…7a05

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

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 0xe99d8e683a…2ea16e

← previous block·next block →recent activity