Block #72,399,799

← previous blocknext block →recent activity

Analyzing

Block #72,399,799

20 transactions · 14 stateful · 2026-05-04 15:05:53 UTC

Parallelism

85/100

Blocked

43%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,399,799  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x1f8b7f41…58ac

0xd32edf…ff58

5 touches
3 conflicts

0x1f131bcd…1b0f

0x34b655…2a6f

4 touches
1 conflict

0x20ac0567…c954

0x34b655…2a6f

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x35e1da0f…f897

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x66efe179…bdc8

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity