Block #71,172,032

← previous blocknext block →recent activity

Analyzing

Block #71,172,032

10 transactions · 9 stateful · 2026-04-28 22:38:32 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,172,032  ·  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

0x86dd167b…0bc4

0x065c9d…c394

6 touches
3 conflicts

0xba0ec841…f74f

0x065c9d…c394

6 touches
3 conflicts

0xd4fd2447…26ad

0x065c9d…c394

6 touches
3 conflicts

0xe2b00516…2369

0x065c9d…c394

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x468c69b1…af11

0x8d66a4…3095

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity