Block #72,296,333

← previous blocknext block →recent activity

Analyzing

Block #72,296,333

11 transactions · 10 stateful · 2026-05-04 03:36:32 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,296,333  ·  11 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

0xa2a78c06…344a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0222ecda…56b1

0x065c9d…c394

3 touches
1 conflict

0x22473194…66f7

0x065c9d…c394

2 touches
0 conflicts

0x230d4a5b…2b93

0x065c9d…c394

2 touches
0 conflicts

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x5b127bd7…ee7c

0x065c9d…c394

2 touches
0 conflicts

0xf5846bf7…4b69

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 0xa2a78c064f…3c344a

← previous block·next block →recent activity