Block #71,703,971

← previous blocknext block →recent activity

Analyzing

Block #71,703,971

11 transactions · 10 stateful · 2026-05-01 09:44:47 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,703,971  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x433e2a5b…638d

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xcbd23469…a4df

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

2 touches
0 conflicts

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x08abfabe…4041

0x6657d1…8ccc

2 touches
0 conflicts

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

1 conflict on slot 0x433e2a5b03…8e638d

← previous block·next block →recent activity