Block #72,288,379

← previous blocknext block →recent activity

Analyzing

Block #72,288,379

10 transactions · 9 stateful · 2026-05-04 02:43:08 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,288,379  ·  10 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

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0x3ab8d0ea…6a7e

0x065c9d…c394

4 touches
1 conflict

0x07e4d1e1…29de

0x34b655…2a6f

4 touches
1 conflict

0x0c70e800…d8f7

0x34b655…2a6f

4 touches
1 conflict

0x0cf2a2bb…7773

0x34b655…2a6f

4 touches
1 conflict

0x116213e6…b8ce

0x34b655…2a6f

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

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