Block #72,228,403

← previous blocknext block →recent activity

Analyzing

Block #72,228,403

9 transactions · 6 stateful · 2026-05-03 20:00:00 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,228,403  ·  9 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcada175e…40a0

0x065c9d…c394

4 touches
1 conflict

0x703fa04a…4825

0x065c9d…c394

3 touches
1 conflict

0x06ab1f3b…5fbf

0x065c9d…c394

3 touches
1 conflict

0x7b4f57fd…0231

0x065c9d…c394

2 touches
0 conflicts

0x80160b33…10e4

0x065c9d…c394

2 touches
0 conflicts

0xfe735f9a…c94a

0x065c9d…c394

2 touches
0 conflicts

0xff3eb40b…7583

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 0x0000000000…00003d

← previous block·next block →recent activity