Block #71,065,781

← previous blocknext block →recent activity

Analyzing

Block #71,065,781

10 transactions · 9 stateful · 2026-04-28 10:50:44 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,065,781  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x3fe7615a…1162

0x065c9d…c394

4 touches
1 conflict

0x9c46a1a1…2f7f

0x065c9d…c394

4 touches
1 conflict

0xd28d4f05…f4fa

0x065c9d…c394

4 touches
1 conflict

0xd3d7b465…e79c

0x065c9d…c394

4 touches
1 conflict

0x749f76ef…1a8c

0x065c9d…c394

2 touches
0 conflicts

0x74df77b5…3378

0x065c9d…c394

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity