Block #71,560,488

← previous blocknext block →recent activity

Analyzing

Block #71,560,488

11 transactions · 11 stateful · 2026-04-30 17:49:49 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,560,488  ·  11 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

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x945c6b0b…1f7c

0x065c9d…c394

4 touches
1 conflict

0x00dd5614…0f1e

0x065c9d…c394

3 touches
1 conflict

0x2c281d84…1d3e

0x065c9d…c394

3 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x1e6db1fe…8d8b

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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 0x348fda08cf…fc7e96

← previous block·next block →recent activity