Block #72,283,233

← previous blocknext block →recent activity

Analyzing

Block #72,283,233

11 transactions · 11 stateful · 2026-05-04 02:08:33 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,283,233  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0xc3aacf13…6b3d

0x34b655…2a6f

4 touches
1 conflict

0xd7a2b02f…1da4

0x34b655…2a6f

4 touches
1 conflict

0xe54a1f6f…18f2

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity