← previous blocknext block →recent activity

Analyzing

Block #74,257,732

9 transactions · 6 stateful · 2026-05-13 05:32:11 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,257,732  ·  9 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

0x10b642bd…b94e

0x065c9d…c394

4 touches
1 conflict

0xf81f3858…12fe

0x065c9d…c394

3 touches
1 conflict

0x5444ac4e…a234

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0db18332…7f6f

0x065c9d…c394

2 touches
0 conflicts

0x35190c30…59e6

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xf823e97f…2ee6

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 0x10b642bd55…e7b94e

← previous block·next block →recent activity