Block #72,301,141

← previous blocknext block →recent activity

Analyzing

Block #72,301,141

10 transactions · 9 stateful · 2026-05-04 04:08:34 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,141  ·  10 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

0x01670cd7…eeaf

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x94c7df2b…bc4c

0x065c9d…c394

3 touches
1 conflict

0xaae89d8f…0f1e

0x065c9d…c394

3 touches
1 conflict

0x1bfaf01c…075d

0x065c9d…c394

2 touches
0 conflicts

0x540b21aa…47bb

0x065c9d…c394

2 touches
0 conflicts

0x90c1fed7…8337

0x065c9d…c394

2 touches
0 conflicts

0xe251ab14…ad5b

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 0x01670cd7a2…c2eeaf

← previous block·next block →recent activity