Block #71,042,482

← previous blocknext block →recent activity

Analyzing

Block #71,042,482

7 transactions · 6 stateful · 2026-04-28 08:15:38 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,042,482  ·  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…0004

0xd0f8a6…badc

4 touches
1 conflict

0x79f22ee8…4049

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x211e1069…7a50

0x065c9d…c394

4 touches
1 conflict

0xf6c1d422…ca12

0x065c9d…c394

3 touches
1 conflict

0xb2a7f9a3…e0f1

0x065c9d…c394

3 touches
1 conflict

0x7b2e62ef…59e5

0x065c9d…c394

2 touches
1 conflict

0x33de42dc…c4cb

0x065c9d…c394

2 touches
1 conflict

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: 0xd0f8a642…83badc

1 conflict on slot 0x0000000000…000004

← previous block·next block →recent activity