Block #72,976,130

← previous blocknext block →recent activity

Analyzing

Block #72,976,130

16 transactions · 12 stateful · 2026-05-07 07:05:39 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,976,130  ·  16 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

0xdaca243a…f9de

0x34b655…2a6f

10 touches
10 conflicts

0xd1efe2a0…3c60

0x34b655…2a6f

6 touches
3 conflicts

0xdf671536…aa02

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x27132f04…5caa

0x34b655…2a6f

6 touches
3 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 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 0xdaca243a5e…09f9de

← previous block·next block →recent activity