Block #72,228,700

← previous blocknext block →recent activity

Analyzing

Block #72,228,700

9 transactions · 8 stateful · 2026-05-03 20:02:01 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x62c2dbc4…f787

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7cc41e8b…f224

0x065c9d…c394

3 touches
1 conflict

0xad440dee…3cde

0x065c9d…c394

3 touches
1 conflict

0x62d82f48…f0d5

0x065c9d…c394

2 touches
0 conflicts

0x70aa6cc2…a20a

0x065c9d…c394

2 touches
0 conflicts

0x962f5d27…5da7

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 0x62c2dbc4ef…61f787

← previous block·next block →recent activity