← previous blocknext block →recent activity

Analyzing

Block #83,844,050

30 transactions · 29 stateful · 2026-06-26 15:34:38 UTC

Parallelism

80/100

Blocked

66%

Avg conflicts / tx

1.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,844,050  ·  30 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x7b7af531…48f1

0xa6afd3…d132

10 touches
10 conflicts

0x5df6102c…6494

0xa6afd3…d132

10 touches
10 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0xd996735f…8735

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…0012

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