Block #72,500,973

← previous blocknext block →recent activity

Analyzing

Block #72,500,973

5 transactions · 4 stateful · 2026-05-05 02:19:43 UTC

Parallelism

60/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,500,973  ·  5 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

0x67822b7c…4860

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdd0367d1…9f3e

0x065c9d…c394

3 touches
1 conflict

0x741b7341…1de0

0x065c9d…c394

3 touches
1 conflict

0x59a992b4…3a62

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x712da18a…e9d5

0x065c9d…c394

2 touches
0 conflicts

0xa8b4ae43…5c52

0x065c9d…c394

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 0x67822b7c8f…d94860

← previous block·next block →recent activity