Block #72,228,497

← previous blocknext block →recent activity

Analyzing

Block #72,228,497

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

Parallelism

83/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x62a0d533…8c38

0x065c9d…c394

4 touches
1 conflict

0x1598d2bc…aef7

0x065c9d…c394

3 touches
1 conflict

0x58538f86…185d

0x065c9d…c394

3 touches
1 conflict

0x62c2dbc4…f787

0x065c9d…c394

2 touches
0 conflicts

0x8fc3cb51…dad8

0x065c9d…c394

2 touches
0 conflicts

0xaf764eaf…fdd8

0x065c9d…c394

2 touches
0 conflicts

0xb24a1aff…ef9f

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