Block #71,555,739

← previous blocknext block →recent activity

Analyzing

Block #71,555,739

35 transactions · 20 stateful · 2026-04-30 17:18:07 UTC

Parallelism

77/100

Blocked

55%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,555,739  ·  35 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

12 touches
15 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x3c35979a…975d

0x34b655…2a6f

8 touches
6 conflicts

0x35b65947…44d1

0xc8689a…ee79

8 touches
6 conflicts

0x085df2c1…305a

0x34b655…2a6f

8 touches
6 conflicts

0x65e795ca…0320

0x34b655…2a6f

8 touches
6 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity