Block #71,744,157

← previous blocknext block →recent activity

Analyzing

Block #71,744,157

14 transactions · 11 stateful · 2026-05-01 14:12:27 UTC

Parallelism

86/100

Blocked

36%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,744,157  ·  14 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

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0xe68e32b2…4a52

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x9119e579…4c58

0x065c9d…c394

3 touches
1 conflict

0x6086cd23…1528

0x065c9d…c394

3 touches
1 conflict

0x1a4b4152…0a08

0x33663b…4897

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: 0x34b6552d…112a6f

1 conflict on slot 0x85a88798de…47f85e

← previous block·next block →recent activity