Block #71,683,675

← previous blocknext block →recent activity

Analyzing

Block #71,683,675

12 transactions · 11 stateful · 2026-05-01 07:29:40 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,683,675  ·  12 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

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x8a6bf757…e368

0x065c9d…c394

4 touches
1 conflict

0x1fa11f78…1bc7

0x065c9d…c394

4 touches
1 conflict

0x78d0c6db…3d8a

0x065c9d…c394

3 touches
1 conflict

0xda336472…6b02

0x065c9d…c394

3 touches
1 conflict

0x508387de…c644

0x2a68ba…90c5

2 touches
0 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

2 touches
0 conflicts

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 0x4175529119…79977f

← previous block·next block →recent activity