← previous blocknext block →recent activity

Analyzing

Block #74,450,510

33 transactions · 24 stateful · 2026-05-14 02:54:51 UTC

Parallelism

82/100

Blocked

63%

Avg conflicts / tx

1.12

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,450,510  ·  33 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x2376c3e1…833a

0xd32edf…ff58

7 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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity