← previous blocknext block →recent activity

Analyzing

Block #74,514,175

13 transactions · 11 stateful · 2026-05-14 09:59:37 UTC

Parallelism

85/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,514,175  ·  13 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

0x4b31d9e7…1dad

0x065c9d…c394

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x0872abbe…9c39

0x2a68ba…90c5

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xcb2e5eca…8036

0x065c9d…c394

3 touches
1 conflict

0xa37148b8…5380

0x065c9d…c394

3 touches
1 conflict

0xb19629f8…81b3

0x065c9d…c394

3 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

1 conflict on slot 0x4b31d9e71d…e61dad

← previous block·next block →recent activity