← previous blocknext block →recent activity

Analyzing

Block #72,226,699

10 transactions · 8 stateful · 2026-05-03 19:48:33 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,226,699  ·  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

0x533373af…f5f9

0x065c9d…c394

4 touches
1 conflict

0x8a9753c6…5267

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x30a42690…559c

0x065c9d…c394

3 touches
1 conflict

0x41eb5aa0…1f9e

0x065c9d…c394

3 touches
1 conflict

0x342eaafb…0df9

0x065c9d…c394

3 touches
1 conflict

0xef31ee52…dbbe

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 0x533373afe5…5ff5f9

← previous block·next block →recent activity