Block #71,746,253

← previous blocknext block →recent activity

Analyzing

Block #71,746,253

22 transactions · 17 stateful · 2026-05-01 14:26:26 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,746,253  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x609ea8fc…245f

0xd32edf…ff58

5 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6caf33e2…c261

0x34b655…2a6f

4 touches
1 conflict

0x6d1ccb53…6db8

0x34b655…2a6f

4 touches
1 conflict

0x831f75b4…945d

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity