Block #71,239,386

← previous blocknext block →recent activity

Analyzing

Block #71,239,386

10 transactions · 8 stateful · 2026-04-29 06:06:34 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,239,386  ·  10 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

0xb2c6bbf1…1150

0x065c9d…c394

4 touches
1 conflict

0xdc85546c…9217

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x43c0f5c0…250f

0x065c9d…c394

3 touches
1 conflict

0xf7aea5dc…dae0

0x065c9d…c394

3 touches
1 conflict

0x578e7f66…1b56

0x34b655…2a6f

2 touches
0 conflicts

0x77905798…fe3d

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 0xb2c6bbf1e0…971150

← previous block·next block →recent activity