← previous blocknext block →recent activity

Analyzing

Block #74,353,277

26 transactions · 21 stateful · 2026-05-13 16:07:37 UTC

Parallelism

77/100

Blocked

48%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,353,277  ·  26 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

0x41755291…977f

0x065c9d…c394

10 touches
10 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x49cf9d85…803a

0xd32edf…ff58

5 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

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: 0x065c9d28…a9c394

10 conflicts on slot 0x4175529119…79977f

← previous block·next block →recent activity