← previous blocknext block →recent activity

Analyzing

Block #72,979,724

10 transactions · 8 stateful · 2026-05-07 07:29:33 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,979,724  ·  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

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6ca43f…c331

4 touches
1 conflict

0x5b3dfef8…a676

0x6ca43f…c331

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x10b51239…21f3

0x065c9d…c394

4 touches
1 conflict

0x1b7e9d60…1afa

0x065c9d…c394

4 touches
1 conflict

0x4056fdfb…b9c7

0x065c9d…c394

4 touches
1 conflict

0x44bb1ea6…a0bd

0x065c9d…c394

4 touches
1 conflict

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: 0xc8689a47…62ee79

1 conflict on slot 0x4e5ebbf7fb…3fae70

← previous block·next block →recent activity