Block #72,233,586

← previous blocknext block →recent activity

Analyzing

Block #72,233,586

8 transactions · 7 stateful · 2026-05-03 20:34:52 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa791b18e…7a7b

0x065c9d…c394

4 touches
1 conflict

0x6ce8091f…d247

0xd32edf…ff58

3 touches
1 conflict

0x6a2cf389…ea4a

0x065c9d…c394

3 touches
1 conflict

0x6a2cf389…ea4b

0x065c9d…c394

3 touches
1 conflict

0xa0d20574…28e1

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x3e4b8d9f…b8a7

0x8d0464…4402

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