Block #71,746,513

← previous blocknext block →recent activity

Analyzing

Block #71,746,513

9 transactions · 7 stateful · 2026-05-01 14:28:10 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,746,513  ·  9 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

0xebb1b07a…9d9c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x592e2d02…0e71

0x065c9d…c394

3 touches
1 conflict

0x999d60fe…4992

0x065c9d…c394

3 touches
1 conflict

0x6d1ce26b…babb

0x065c9d…c394

3 touches
1 conflict

0x80e12964…501d

0x065c9d…c394

3 touches
1 conflict

0x2e2214a9…fe0d

0x33663b…4897

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 0xebb1b07a7c…b19d9c

← previous block·next block →recent activity