Block #71,701,409

← previous blocknext block →recent activity

Analyzing

Block #71,701,409

6 transactions · 5 stateful · 2026-05-01 09:27:42 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,701,409  ·  6 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

0x2a37152b…a7c5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x55a00292…9489

0x065c9d…c394

3 touches
1 conflict

0x3e77cd38…4b4a

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x51469d0b…754c

0x065c9d…c394

2 touches
0 conflicts

0xfcbfe6d6…d1f8

0x065c9d…c394

2 touches
0 conflicts

0x508387de…c644

0x2a68ba…90c5

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 0x2a37152bae…19a7c5

← previous block·next block →recent activity