Block #72,228,410

← previous blocknext block →recent activity

Analyzing

Block #72,228,410

16 transactions · 12 stateful · 2026-05-03 20:00:03 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,228,410  ·  16 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

0x0d7fcda3…d2e2

0xd32edf…ff58

5 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x65d866c8…a265

0x065c9d…c394

4 touches
1 conflict

0xbe094a7f…539c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbf04f37d…85f2

0x2a68ba…90c5

4 touches
1 conflict

0x7f4c409a…2211

0x065c9d…c394

3 touches
1 conflict

0x03510b81…b70f

0x065c9d…c394

3 touches
1 conflict

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: 0xd32edf66…9fff58

3 conflicts on slot 0x0d7fcda34a…6bd2e2

← previous block·next block →recent activity