Block #71,701,945

← previous blocknext block →recent activity

Analyzing

Block #71,701,945

13 transactions · 12 stateful · 2026-05-01 09:31:17 UTC

Parallelism

85/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xcdd22abc…3837

0x065c9d…c394

4 touches
1 conflict

0xd63729fb…c0ec

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf3bc88de…cc9f

0x065c9d…c394

3 touches
1 conflict

0x2db7692c…5289

0x065c9d…c394

3 touches
1 conflict

0x12eb3afe…2b92

0x065c9d…c394

3 touches
1 conflict

0x33bc0eb0…ed53

0x065c9d…c394

3 touches
1 conflict

0x81a7ba4d…8c4b

0x23c26b…7777

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 0xcdd22abc78…c53837

← previous block·next block →recent activity