Block #71,683,654

← previous blocknext block →recent activity

Analyzing

Block #71,683,654

14 transactions · 14 stateful · 2026-05-01 07:29:32 UTC

Parallelism

57/100

Blocked

43%

Avg conflicts / tx

1.21

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,683,654  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x38c85224…a905

0xd32edf…ff58

11 touches
15 conflicts

0xe5209d89…7559

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xb4709067…1267

0x065c9d…c394

3 touches
1 conflict

0x786e7a25…6f93

0x065c9d…c394

3 touches
1 conflict

0xf9e935ed…11c9

0x065c9d…c394

3 touches
1 conflict

0x0c86bbe4…fffd

0x5afd3e…7620

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: 0xd32edf66…9fff58

15 conflicts on slot 0x38c8522447…e9a905

← previous block·next block →recent activity