Block #71,041,963

← previous blocknext block →recent activity

Analyzing

Block #71,041,963

10 transactions · 9 stateful · 2026-04-28 08:12:10 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,041,963  ·  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

0xbc193a09…0b4a

0x065c9d…c394

4 touches
1 conflict

0xed4aec2d…c088

0x065c9d…c394

4 touches
1 conflict

0xf0493190…b20b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x28e259b6…8e20

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x25de453d…9573

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 0xbc193a0965…920b4a

← previous block·next block →recent activity