Block #71,683,729

← previous blocknext block →recent activity

Analyzing

Block #71,683,729

10 transactions · 8 stateful · 2026-05-01 07:30:01 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,683,729  ·  10 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

0x1ec9eac3…f6cb

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0xe889cb2c…5206

0x065c9d…c394

3 touches
1 conflict

0x9dc696c5…10af

0x065c9d…c394

3 touches
1 conflict

0x489a9621…cd35

0x065c9d…c394

3 touches
1 conflict

0x4e1654e5…90cf

0x065c9d…c394

3 touches
1 conflict

0x1a4b4152…0a08

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 0x1ec9eac30c…c9f6cb

← previous block·next block →recent activity