← previous blocknext block →recent activity

Analyzing

Block #74,247,608

21 transactions · 11 stateful · 2026-05-13 04:24:55 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,247,608  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb0a5ede8…4015

0xd32edf…ff58

9 touches
10 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c6

0x1b6862…e19c

2 touches
0 conflicts

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 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 0xb0a5ede8f9…a44015

← previous block·next block →recent activity