Block #72,233,268

← previous blocknext block →recent activity

Analyzing

Block #72,233,268

7 transactions · 7 stateful · 2026-05-03 20:32:45 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,233,268  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x1c3fff0f…9049

0x065c9d…c394

4 touches
1 conflict

0xf58e5723…2f8a

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x994a9b16…87d6

0x065c9d…c394

2 touches
0 conflicts

0x9bdd2a11…e1e0

0x065c9d…c394

2 touches
0 conflicts

0x9c46a1a1…2f7f

0x065c9d…c394

2 touches
0 conflicts

0xa62a7aef…ee84

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity