Block #72,285,766

← previous blocknext block →recent activity

Analyzing

Block #72,285,766

16 transactions · 11 stateful · 2026-05-04 02:25:35 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,285,766  ·  16 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

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x9ba7a527…1114

0x065c9d…c394

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x077d8451…54fb

0x065c9d…c394

3 touches
1 conflict

0x8714edf0…52b6

0x065c9d…c394

3 touches
1 conflict

0x51c729da…58fd

0x065c9d…c394

3 touches
1 conflict

0x00000000…0002

0x63e48b…53f2

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity