Block #71,177,228

← previous blocknext block →recent activity

Analyzing

Block #71,177,228

12 transactions · 10 stateful · 2026-04-28 23:13:06 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,177,228  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x468c69b1…af11

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x78067279…d187

0x34b655…2a6f

4 touches
1 conflict

0xb409e204…89ac

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity