← previous blocknext block →recent activity

Analyzing

Block #76,167,152

31 transactions · 28 stateful · 2026-05-22 02:03:39 UTC

Parallelism

65/100

Blocked

75%

Avg conflicts / tx

2.23

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #76,167,152  ·  31 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x699e5877…05ab

0x34b655…2a6f

10 touches
10 conflicts

0x6ba4f479…7943

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c5

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x99a21305…dffc

0x2a68ba…90c5

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity