← previous blocknext block →recent activity

Analyzing

Block #84,334,267

33 transactions · 30 stateful · 2026-06-28 22:00:42 UTC

Parallelism

79/100

Blocked

57%

Avg conflicts / tx

1.64

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #84,334,267  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x00000000…003d

0xa6afd3…d132

12 touches
15 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x5da4ed2f…283f

0xa6afd3…d132

10 touches
10 conflicts

0xcb9de9a9…e355

0xd32edf…ff58

9 touches
10 conflicts

0xba5743c7…21c0

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x75194ada…a1c5

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

21 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity