← previous blocknext block →recent activity

Analyzing

Block #74,359,701

11 transactions · 8 stateful · 2026-05-13 16:50:22 UTC

Parallelism

73/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,359,701  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x1f9be478…e25e

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x002747df…c595

0x065c9d…c394

3 touches
1 conflict

0x992d56e6…7659

0x065c9d…c394

3 touches
1 conflict

0x54535367…9e97

0x065c9d…c394

2 touches
0 conflicts

0x697aea01…f472

0x065c9d…c394

2 touches
0 conflicts

0x738b60d0…3f25

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 0x1f9be47896…7ce25e

← previous block·next block →recent activity