Block #72,575,740

← previous blocknext block →recent activity

Analyzing

Block #72,575,740

6 transactions · 5 stateful · 2026-05-05 10:37:34 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,575,740  ·  6 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

0x45e1f3e8…783d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x98c85b29…a042

0x065c9d…c394

3 touches
1 conflict

0x0b84724f…6a5b

0x065c9d…c394

2 touches
0 conflicts

0x4b377f39…3ab0

0x065c9d…c394

2 touches
0 conflicts

0xb5078851…4c44

0x065c9d…c394

2 touches
0 conflicts

0xb6e3280f…6b3d

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

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 0x45e1f3e878…02783d

← previous block·next block →recent activity