← previous blocknext block →recent activity

Analyzing

Block #80,678,594

35 transactions · 23 stateful · 2026-06-11 23:33:24 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.86

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #80,678,594  ·  35 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x81e1f4e8…08d7

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2f68ff96…38a6

0x34b655…2a6f

5 touches
3 conflicts

0xb409e204…89ac

0x34b655…2a6f

4 touches
1 conflict

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity