Block #72,400,041

← previous blocknext block →recent activity

Analyzing

Block #72,400,041

21 transactions · 17 stateful · 2026-05-04 15:07:30 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,400,041  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0xd7a2b02f…1da4

0x34b655…2a6f

8 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0xf22dac61…b0ae

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

8 touches
6 conflicts

0x23951077…539b

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