Block #71,449,337

← previous blocknext block →recent activity

Analyzing

Block #71,449,337

18 transactions · 17 stateful · 2026-04-30 05:25:34 UTC

Parallelism

50/100

Blocked

59%

Avg conflicts / tx

1.5

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,449,337  ·  18 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x21d6593f…26e1

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x32ee90db…decc

0x34b655…2a6f

6 touches
3 conflicts

0x5728edaf…f1d4

0x34b655…2a6f

6 touches
3 conflicts

0x578e7f66…1b56

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0x21d6593f38…9526e1

← previous block·next block →recent activity