← previous blocknext block →recent activity

Analyzing

Block #74,472,992

10 transactions · 9 stateful · 2026-05-14 05:24:28 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,472,992  ·  10 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x8f478f26…9d56

0x000000…012a

2 touches
0 conflicts

0x9cafc3b6…ee8c

0x000000…012a

2 touches
0 conflicts

0x00000000…0036

0x386489…7508

2 touches
0 conflicts

0x1a920eda…bfae

0x386489…7508

2 touches
0 conflicts

0x15bae5fc…9f7e

0x57ea24…2cec

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity