← previous blocknext block →recent activity

Analyzing

Block #71,559,109

12 transactions · 9 stateful · 2026-04-30 17:40:38 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,559,109  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4ea6b730…6888

0x065c9d…c394

4 touches
1 conflict

0xe57e25d6…498b

0x065c9d…c394

3 touches
1 conflict

0x61f2e040…dc13

0x065c9d…c394

2 touches
0 conflicts

0x0efc210e…70ab

0x34b655…2a6f

2 touches
0 conflicts

0x1849a76a…cfdf

0x34b655…2a6f

2 touches
0 conflicts

0x2557abf8…2901

0x34b655…2a6f

2 touches
0 conflicts

0x3999dac2…802e

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 0x0000000000…00003d

← previous block·next block →recent activity