← previous blocknext block →recent activity

Analyzing

Block #84,254,913

43 transactions · 36 stateful · 2026-06-28 13:12:01 UTC

Parallelism

79/100

Blocked

61%

Avg conflicts / tx

1.23

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #84,254,913  ·  43 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x977cf0a8…d4a3

0xd32edf…ff58

11 touches
15 conflicts

0xe02484a6…c32e

0xc8689a…ee79

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0xe2e45419…f17b

0x34b655…2a6f

8 touches
6 conflicts

0x07b5c6c6…886a

0x1b6862…e19c

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

15 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity