← previous blocknext block →recent activity

Analyzing

Block #74,340,797

13 transactions · 11 stateful · 2026-05-13 14:44:43 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,340,797  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x524af432…9640

0x065c9d…c394

2 touches
0 conflicts

0x9da33b32…cc28

0x065c9d…c394

2 touches
0 conflicts

0x9ec24126…150e

0x065c9d…c394

2 touches
0 conflicts

0xc1e027f8…3871

0x065c9d…c394

2 touches
0 conflicts

0xc22f32f3…9383

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity