← previous blocknext block →recent activity

Analyzing

Block #74,415,093

11 transactions · 8 stateful · 2026-05-13 22:59:06 UTC

Parallelism

82/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,415,093  ·  11 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd42f5741…3915

0x065c9d…c394

3 touches
1 conflict

0x14c70861…422b

0x065c9d…c394

2 touches
0 conflicts

0x5a0a316d…ba8d

0x065c9d…c394

2 touches
0 conflicts

0x6f51b2b2…56a0

0x065c9d…c394

2 touches
0 conflicts

0xa0f9be8f…ef60

0x065c9d…c394

2 touches
0 conflicts

0xdf6434bc…c225

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity