Block #71,417,728

← previous blocknext block →recent activity

Analyzing

Block #71,417,728

23 transactions · 23 stateful · 2026-04-30 01:54:56 UTC

Parallelism

61/100

Blocked

61%

Avg conflicts / tx

2.22

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,417,728  ·  23 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

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

12 touches
15 conflicts

0x21d22421…0b7a

0x34b655…2a6f

10 touches
10 conflicts

0x2877f440…c2c8

0x34b655…2a6f

10 touches
10 conflicts

0x3254d19b…f714

0x34b655…2a6f

10 touches
10 conflicts

0x3b74ae43…a235

0x34b655…2a6f

10 touches
10 conflicts

0x414e9446…4b59

0x34b655…2a6f

10 touches
10 conflicts

0x51500297…20aa

0x34b655…2a6f

10 touches
10 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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity