← previous blocknext block →recent activity

Analyzing

Block #74,464,804

34 transactions · 23 stateful · 2026-05-14 04:30:04 UTC

Parallelism

74/100

Blocked

61%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,464,804  ·  34 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

0xc73d6250…7728

0xd32edf…ff58

11 touches
15 conflicts

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

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

15 conflicts on slot 0xc73d625073…e27728

← previous block·next block →recent activity