← previous blocknext block →recent activity

Analyzing

Block #74,204,609

9 transactions · 7 stateful · 2026-05-12 23:39:01 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,204,609  ·  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

0x3fd363af…8333

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x6faa7109…b832

0x065c9d…c394

2 touches
0 conflicts

0xe672462d…8a49

0x065c9d…c394

2 touches
0 conflicts

0xe813febb…e543

0x065c9d…c394

2 touches
0 conflicts

0xf073d628…282b

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 0x3fd363afa2…d88333

← previous block·next block →recent activity