Block #72,226,258

← previous blocknext block →recent activity

Analyzing

Block #72,226,258

7 transactions · 6 stateful · 2026-05-03 19:45:35 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x7de52747…4a70

0x065c9d…c394

4 touches
1 conflict

0x345667db…c4b7

0x065c9d…c394

4 touches
1 conflict

0x9be83885…e718

0x065c9d…c394

3 touches
1 conflict

0x6c5dee78…e640

0x065c9d…c394

3 touches
1 conflict

0x0aca480c…2f9b

0x065c9d…c394

3 touches
1 conflict

0x79358492…f219

0x065c9d…c394

2 touches
0 conflicts

0x7f1c4cef…9825

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