Block #72,228,373

← previous blocknext block →recent activity

Analyzing

Block #72,228,373

8 transactions · 6 stateful · 2026-05-03 19:59:48 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x227834b8…253f

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa45aaef2…8c08

0x065c9d…c394

3 touches
1 conflict

0x19c1369e…6a23

0x065c9d…c394

3 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x4a498513…fcb2

0x065c9d…c394

2 touches
0 conflicts

0x54d30527…6f0c

0x065c9d…c394

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

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 0x227834b890…66253f

← previous block·next block →recent activity