← previous blocknext block →recent activity

Analyzing

Block #74,624,419

9 transactions · 7 stateful · 2026-05-14 22:20:07 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,624,419  ·  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

0xc56c2f0d…c545

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc30b4e58…1038

0x065c9d…c394

3 touches
1 conflict

0x24ddedbf…c4b0

0x065c9d…c394

2 touches
0 conflicts

0x4f44f2d1…5327

0x065c9d…c394

2 touches
0 conflicts

0xb8db3d3a…3e3e

0x065c9d…c394

2 touches
0 conflicts

0xf373c0de…7264

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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 0xc56c2f0dd2…15c545

← previous block·next block →recent activity