← previous blocknext block →recent activity

Analyzing

Block #74,479,510

12 transactions · 9 stateful · 2026-05-14 06:07:52 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,479,510  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x7e709c41…b0df

0x065c9d…c394

4 touches
1 conflict

0x3d24ae17…9211

0x065c9d…c394

3 touches
1 conflict

0x19bf52d2…b9cb

0x065c9d…c394

3 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x95365e4f…b0a3

0x065c9d…c394

2 touches
0 conflicts

0xf0cd8cdd…1a55

0x065c9d…c394

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

1 conflict on slot 0x7e709c4147…7fb0df

← previous block·next block →recent activity