← previous blocknext block →recent activity

Analyzing

Block #80,822,634

48 transactions · 38 stateful · 2026-06-12 15:33:53 UTC

Parallelism

75/100

Blocked

66%

Avg conflicts / tx

1.58

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #80,822,634  ·  48 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

10 touches
10 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0x3293a887…4400

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity