Block #72,233,179

← previous blocknext block →recent activity

Analyzing

Block #72,233,179

10 transactions · 9 stateful · 2026-05-03 20:32:09 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,233,179  ·  10 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

0xb17ed949…fec4

0x065c9d…c394

4 touches
1 conflict

0x04d674b5…64f0

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2cdcf2bf…711e

0x065c9d…c394

3 touches
1 conflict

0x5904daa3…6fa4

0x065c9d…c394

3 touches
1 conflict

0x8ecc0451…5e7f

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x856bf2c4…137b

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 0xb17ed94933…5afec4

← previous block·next block →recent activity