← previous blocknext block →recent activity

Analyzing

Block #74,032,665

15 transactions · 13 stateful · 2026-05-12 04:35:02 UTC

Parallelism

73/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,032,665  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xfab6fc6d…3a4d

0xd32edf…ff58

7 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x35cbeb39…151a

0x065c9d…c394

2 touches
0 conflicts

0x6cfc14a6…6b1b

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

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

6 conflicts on slot 0xfab6fc6d62…3e3a4d

← previous block·next block →recent activity