← previous blocknext block →recent activity

Analyzing

Block #72,371,253

10 transactions · 7 stateful · 2026-05-04 11:55:34 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,371,253  ·  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

0x2afc645d…40a4

0x065c9d…c394

4 touches
1 conflict

0xd0981e18…291b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x1a36d156…c698

0x065c9d…c394

4 touches
1 conflict

0x6f333a29…9827

0x065c9d…c394

3 touches
1 conflict

0xf2d0adbe…b31d

0x065c9d…c394

3 touches
1 conflict

0x3b4423dc…b40b

0x065c9d…c394

3 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: 0x065c9d28…a9c394

1 conflict on slot 0x2afc645db7…7740a4

← previous block·next block →recent activity