Block #71,172,228

← previous blocknext block →recent activity

Analyzing

Block #71,172,228

14 transactions · 13 stateful · 2026-04-28 22:39:51 UTC

Parallelism

57/100

Blocked

38%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,172,228  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd85f8d65…3f32

0x065c9d…c394

7 touches
6 conflicts

0xf487a2f4…aa1f

0xd32edf…ff58

7 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c1

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

6 conflicts on slot 0xd85f8d659e…683f32

← previous block·next block →recent activity