← previous blocknext block →recent activity

Analyzing

Block #74,410,580

25 transactions · 21 stateful · 2026-05-13 22:29:10 UTC

Parallelism

76/100

Blocked

57%

Avg conflicts / tx

0.96

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,410,580  ·  25 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

0xd0eba6d5…45b4

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0x73912233…4585

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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

10 conflicts on slot 0xd0eba6d51d…9945b4

← previous block·next block →recent activity