Block #72,286,096

← previous blocknext block →recent activity

Analyzing

Block #72,286,096

10 transactions · 9 stateful · 2026-05-04 02:27:48 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,286,096  ·  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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdf182022…d199

0x065c9d…c394

3 touches
1 conflict

0xd4e962f8…5d60

0x065c9d…c394

3 touches
1 conflict

0xcdb9ffb4…41c0

0x065c9d…c394

3 touches
1 conflict

0x8966f96b…fde8

0x065c9d…c394

3 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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity