Block #72,284,405

← previous blocknext block →recent activity

Analyzing

Block #72,284,405

18 transactions · 14 stateful · 2026-05-04 02:16:24 UTC

Parallelism

78/100

Blocked

43%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,284,405  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x88915805…fbc9

0x34b655…2a6f

6 touches
3 conflicts

0x38a760d6…d599

0x065c9d…c394

4 touches
1 conflict

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xfbabb02d…af07

0x34b655…2a6f

4 touches
1 conflict

0x08943ea2…ed03

0x754704…b603

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity