Block #71,688,333

← previous blocknext block →recent activity

Analyzing

Block #71,688,333

20 transactions · 11 stateful · 2026-05-01 08:00:40 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,688,333  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb349333d…970c

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x607d9ded…6b28

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x41a5c4a1…f478

0x065c9d…c394

3 touches
1 conflict

0x46520403…97d1

0x065c9d…c394

3 touches
1 conflict

0x4c65a6ae…c5a6

0x065c9d…c394

3 touches
1 conflict

0x4e7ce082…6a38

0x065c9d…c394

3 touches
1 conflict

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: 0xd32edf66…9fff58

6 conflicts on slot 0xb349333dc0…d6970c

← previous block·next block →recent activity