Block #72,399,228

← previous blocknext block →recent activity

Analyzing

Block #72,399,228

7 transactions · 5 stateful · 2026-05-04 15:02:04 UTC

Parallelism

57/100

Blocked

40%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x78208fae…dfb2

0x065c9d…c394

4 touches
1 conflict

0x594c87a6…ef9f

0x065c9d…c394

3 touches
1 conflict

0xf9b9b6c4…a784

0x065c9d…c394

3 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0xf7d1adbe…280d

0x065c9d…c394

2 touches
0 conflicts

0x74e71984…ae90

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity