← previous blocknext block →recent activity

Analyzing

Block #74,527,066

24 transactions · 22 stateful · 2026-05-14 11:26:27 UTC

Parallelism

71/100

Blocked

59%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,527,066  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x79093a97…6ff3

0xd32edf…ff58

11 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…002d

0x1b6862…e19c

10 touches
10 conflicts

0x485d2778…aa5f

0x1b6862…e19c

10 touches
10 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: 0xd32edf66…9fff58

15 conflicts on slot 0x79093a9737…016ff3

← previous block·next block →recent activity