← previous blocknext block →recent activity

Analyzing

Block #74,463,232

20 transactions · 14 stateful · 2026-05-14 04:19:38 UTC

Parallelism

85/100

Blocked

36%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,463,232  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x714eec2d…d34c

0x065c9d…c394

5 touches
3 conflicts

0x52485a48…3166

0x065c9d…c394

5 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x163ec845…6116

0x065c9d…c394

4 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x5d823e…89c6

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

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity