Block #72,399,726

← previous blocknext block →recent activity

Analyzing

Block #72,399,726

9 transactions · 8 stateful · 2026-05-04 15:05:23 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,399,726  ·  9 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x3ae7f225…cda1

0x065c9d…c394

2 touches
0 conflicts

0x4f0818da…d6a8

0x065c9d…c394

2 touches
0 conflicts

0x5704493b…b0f1

0x065c9d…c394

2 touches
0 conflicts

0x626710e1…c520

0x065c9d…c394

2 touches
0 conflicts

0xc6f1b3af…c97c

0x1001ff…1001

2 touches
0 conflicts

0xfbc68ff3…ec66

0x1001ff…1001

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity