Block #72,271,589

← previous blocknext block →recent activity

Analyzing

Block #72,271,589

15 transactions · 9 stateful · 2026-05-04 00:50:17 UTC

Parallelism

87/100

Blocked

11%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,271,589  ·  15 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

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x08073057…5069

0x065c9d…c394

2 touches
0 conflicts

0x1be50d15…789e

0x065c9d…c394

2 touches
0 conflicts

0x379cf9a8…f0fa

0x065c9d…c394

2 touches
0 conflicts

0x62f52ece…d37d

0x065c9d…c394

2 touches
0 conflicts

0x86f469ab…a0b3

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 0x0000000000…00003d

← previous block·next block →recent activity