Block #71,683,630

← previous blocknext block →recent activity

Analyzing

Block #71,683,630

29 transactions · 20 stateful · 2026-05-01 07:29:22 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

1.31

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,683,630  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x4b0a3e02…eada

0xd32edf…ff58

15 touches
28 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

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

28 conflicts on slot 0x4b0a3e02c4…b1eada

← previous block·next block →recent activity