Block #71,688,589

← previous blocknext block →recent activity

Analyzing

Block #71,688,589

15 transactions · 10 stateful · 2026-05-01 08:02:19 UTC

Parallelism

87/100

Blocked

20%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,688,589  ·  15 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

0x1bde0d88…9fcf

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xd5fee5ce…8358

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x0175b7a6…1dbc

0x33663b…4897

2 touches
0 conflicts

0x0175b7a6…1dbd

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: 0x34b6552d…112a6f

1 conflict on slot 0x1bde0d88bf…cc9fcf

← previous block·next block →recent activity