Block #71,741,571

← previous blocknext block →recent activity

Analyzing

Block #71,741,571

34 transactions · 29 stateful · 2026-05-01 13:55:12 UTC

Parallelism

59/100

Blocked

62%

Avg conflicts / tx

2.88

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #71,741,571  ·  34 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0xcbae7578…55fb

0xd32edf…ff58

27 touches
91 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xf2d99ce6…c37a

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 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: 0xd32edf66…9fff58

91 conflicts on slot 0xcbae757863…9e55fb

← previous block·next block →recent activity