Block #71,701,448

← previous blocknext block →recent activity

Analyzing

Block #71,701,448

10 transactions · 10 stateful · 2026-05-01 09:27:58 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbb8f7e8b…da57

0x065c9d…c394

4 touches
1 conflict

0x173aa5b3…2346

0x065c9d…c394

3 touches
1 conflict

0xaeaa621f…a904

0x065c9d…c394

3 touches
1 conflict

0x2aef8981…7de5

0x065c9d…c394

3 touches
1 conflict

0x3e4b02f8…bf0d

0x065c9d…c394

3 touches
1 conflict

0xfbd0c453…ed5d

0x065c9d…c394

2 touches
0 conflicts

0x508387de…c644

0x2a68ba…90c5

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