Block #71,701,579

← previous blocknext block →recent activity

Analyzing

Block #71,701,579

7 transactions · 6 stateful · 2026-05-01 09:28:50 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,701,579  ·  7 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

0x26dd14d2…ccfe

0x065c9d…c394

4 touches
1 conflict

0x9fb427cd…f3c7

0x065c9d…c394

3 touches
1 conflict

0x3b47ae31…db98

0x065c9d…c394

3 touches
1 conflict

0x138e3f85…9271

0x065c9d…c394

2 touches
0 conflicts

0x410f094b…4877

0x065c9d…c394

2 touches
0 conflicts

0x47e9b129…330e

0x065c9d…c394

2 touches
0 conflicts

0xa30beef3…cc13

0x065c9d…c394

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