Block #71,555,640

← previous blocknext block →recent activity

Analyzing

Block #71,555,640

37 transactions · 24 stateful · 2026-04-30 17:17:28 UTC

Parallelism

84/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,555,640  ·  37 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x8902ba1f…f4b6

0x34b655…2a6f

10 touches
10 conflicts

0x2484cc15…5afc

0x34b655…2a6f

8 touches
6 conflicts

0x3d384296…a8c9

0x34b655…2a6f

8 touches
6 conflicts

0x00f245ce…1e10

0x34b655…2a6f

8 touches
6 conflicts

0x50c2960c…5f37

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0x664bf99e…0a8c

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity