Block #72,430,439

← previous blocknext block →recent activity

Analyzing

Block #72,430,439

21 transactions · 14 stateful · 2026-05-04 18:30:01 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,430,439  ·  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

0xd33b6c83…7cd7

0xd32edf…ff58

9 touches
10 conflicts

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x93973335…27bd

0x065c9d…c394

2 touches
0 conflicts

0x94d40b47…0265

0x065c9d…c394

2 touches
0 conflicts

0xc9a2104e…d7d5

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

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: 0xd32edf66…9fff58

10 conflicts on slot 0xd33b6c8305…5a7cd7

← previous block·next block →recent activity