Block #71,037,405

← previous blocknext block →recent activity

Analyzing

Block #71,037,405

8 transactions · 7 stateful · 2026-04-28 07:41:51 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,037,405  ·  8 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

0xa19b3dd9…0bec

0x065c9d…c394

4 touches
1 conflict

0xb0be8456…198c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x40d64c8c…085c

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x95816cdd…6ffb

0x065c9d…c394

4 touches
1 conflict

0x4d4ca84f…c3e8

0x065c9d…c394

2 touches
1 conflict

0x531025bd…5690

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: 0x065c9d28…a9c394

1 conflict on slot 0xa19b3dd940…310bec

← previous block·next block →recent activity