← previous blocknext block →recent activity

Analyzing

Block #74,025,979

41 transactions · 33 stateful · 2026-05-12 03:50:43 UTC

Parallelism

78/100

Blocked

64%

Avg conflicts / tx

1.51

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,025,979  ·  41 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

0x91de52bb…ca24

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0012

0x1b6862…e19c

14 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

14 touches
21 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…001b

0x1b6862…e19c

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 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

36 conflicts on slot 0x91de52bb22…b5ca24

← previous block·next block →recent activity