Block #71,741,515

← previous blocknext block →recent activity

Analyzing

Block #71,741,515

9 transactions · 9 stateful · 2026-05-01 13:54:50 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,741,515  ·  9 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

0xe68e32b2…4a52

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x288cfc8e…e1f7

0x065c9d…c394

3 touches
1 conflict

0x33d69aff…b76f

0x065c9d…c394

3 touches
1 conflict

0xd1f7e0b1…f20d

0x065c9d…c394

3 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001d

0x1b6862…e19c

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 0xe68e32b2d3…4b4a52

← previous block·next block →recent activity