Block #72,228,463

← previous blocknext block →recent activity

Analyzing

Block #72,228,463

13 transactions · 10 stateful · 2026-05-03 20:00:24 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,228,463  ·  13 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

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x4ff1c451…b192

0x065c9d…c394

3 touches
1 conflict

0xb81c8b5b…fe53

0x065c9d…c394

3 touches
1 conflict

0xd3fdc3c4…a179

0x065c9d…c394

3 touches
1 conflict

0x453f38cd…21e0

0x065c9d…c394

2 touches
0 conflicts

0x57e83a30…77bc

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