Block #71,708,711

← previous blocknext block →recent activity

Analyzing

Block #71,708,711

14 transactions · 11 stateful · 2026-05-01 10:16:16 UTC

Parallelism

86/100

Blocked

18%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,708,711  ·  14 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

0x377380c6…6e8c

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x0cc6cea4…47bf

0xd32edf…ff58

3 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x03622417…0bd6

0x2880ab…7b43

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 0x377380c689…966e8c

← previous block·next block →recent activity