Block #72,228,300

← previous blocknext block →recent activity

Analyzing

Block #72,228,300

8 transactions · 7 stateful · 2026-05-03 19:59:18 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,228,300  ·  8 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

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x8a5c8331…8e29

0x065c9d…c394

3 touches
1 conflict

0xd763fff8…2aa8

0x065c9d…c394

3 touches
1 conflict

0x6bd9b2de…7d72

0x0f2610…0edc

2 touches
0 conflicts

0xbf04f37d…85f2

0x2a68ba…90c5

2 touches
0 conflicts

0xed28db8a…3ae7

0x2ae0cf…3d4e

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 0x47b807a243…c53307

← previous block·next block →recent activity