Block #72,575,869

← previous blocknext block →recent activity

Analyzing

Block #72,575,869

13 transactions · 11 stateful · 2026-05-05 10:38:26 UTC

Parallelism

69/100

Blocked

45%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,575,869  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x5658764e…3fd2

0xd32edf…ff58

5 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x24a2d829…f36e

0x065c9d…c394

3 touches
1 conflict

0x2a3d262a…be43

0x065c9d…c394

2 touches
0 conflicts

0x6437ef6e…af67

0x065c9d…c394

2 touches
0 conflicts

0xb38ae625…3d4a

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity