Block #72,224,579

← previous blocknext block →recent activity

Analyzing

Block #72,224,579

10 transactions · 7 stateful · 2026-05-03 19:34:18 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,224,579  ·  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

0x9e0e23b5…6910

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0x5aefd382…5af6

0x065c9d…c394

2 touches
0 conflicts

0x8bcd47a1…87d8

0x065c9d…c394

2 touches
0 conflicts

0xb9c5fe9d…9a43

0x065c9d…c394

2 touches
0 conflicts

0xe3fdcd7c…95de

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: 0x34b6552d…112a6f

1 conflict on slot 0x9e0e23b598…8b6910

← previous block·next block →recent activity