Block #72,283,444

← previous blocknext block →recent activity

Analyzing

Block #72,283,444

8 transactions · 7 stateful · 2026-05-04 02:09:57 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,283,444  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

3 touches
1 conflict

0x6fdc73d3…9853

0x8d66a4…3095

3 touches
1 conflict

0x53c41998…7d52

0x34b655…2a6f

2 touches
0 conflicts

0x76eb9e75…d982

0x34b655…2a6f

2 touches
0 conflicts

0x88915805…fbc9

0x34b655…2a6f

2 touches
0 conflicts

0xa1d7d740…4538

0x34b655…2a6f

2 touches
0 conflicts

0xc824469a…6425

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity