Block #72,399,886

← previous blocknext block →recent activity

Analyzing

Block #72,399,886

16 transactions · 15 stateful · 2026-05-04 15:06:28 UTC

Parallelism

56/100

Blocked

53%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,399,886  ·  16 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

0xe54a1f6f…18f2

0x34b655…2a6f

14 touches
21 conflicts

0xd7a2b02f…1da4

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x99f080dc…58c1

0x34b655…2a6f

12 touches
15 conflicts

0xaa3492db…3703

0x34b655…2a6f

12 touches
15 conflicts

0xac8e97a0…8426

0x34b655…2a6f

12 touches
15 conflicts

0xaef9058e…322a

0x34b655…2a6f

12 touches
15 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

21 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity