Block #71,746,470

← previous blocknext block →recent activity

Analyzing

Block #71,746,470

13 transactions · 9 stateful · 2026-05-01 14:27:53 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xcd53e2c7…fe6e

0x065c9d…c394

4 touches
1 conflict

0x5298e00e…7aef

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x522032fb…84c8

0x065c9d…c394

3 touches
1 conflict

0x33572722…cf3a

0x065c9d…c394

3 touches
1 conflict

0x320261dc…81fe

0x065c9d…c394

3 touches
1 conflict

0x953d8704…b3ea

0x065c9d…c394

3 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

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 0xcd53e2c7f4…d7fe6e

← previous block·next block →recent activity