Block #71,450,870

← previous blocknext block →recent activity

Analyzing

Block #71,450,870

18 transactions · 15 stateful · 2026-04-30 05:35:48 UTC

Parallelism

61/100

Blocked

60%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,450,870  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xb97c885b…2933

0x34b655…2a6f

8 touches
6 conflicts

0x5cc43c33…5bf1

0x34b655…2a6f

6 touches
3 conflicts

0x75f928fc…0465

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc166a323…1f33

0x34b655…2a6f

6 touches
3 conflicts

0x59ef13ba…2741

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity