← previous blocknext block →recent activity

Analyzing

Block #74,764,039

45 transactions · 33 stateful · 2026-05-15 13:52:04 UTC

Parallelism

80/100

Blocked

61%

Avg conflicts / tx

1.36

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,764,039  ·  45 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

0xe09d842b…ff79

0xd32edf…ff58

15 touches
28 conflicts

0x443a3e47…f4a4

0x065c9d…c394

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0x8b41ec8f…c2d5

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

28 conflicts on slot 0xe09d842b8a…feff79

← previous block·next block →recent activity