Block #72,288,374

← previous blocknext block →recent activity

Analyzing

Block #72,288,374

8 transactions · 7 stateful · 2026-05-04 02:43:06 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,288,374  ·  8 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

0x85a1e393…181d

0x065c9d…c394

3 touches
1 conflict

0x5f973ba9…739c

0x065c9d…c394

3 touches
1 conflict

0x694f213c…5e3d

0x065c9d…c394

3 touches
1 conflict

0x0c70e800…d8f7

0x34b655…2a6f

2 touches
0 conflicts

0x0cf2a2bb…7773

0x34b655…2a6f

2 touches
0 conflicts

0x0d39394f…963f

0x34b655…2a6f

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x270826ca…72b4

0x34b655…2a6f

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 0x85a1e3931c…e9181d

← previous block·next block →recent activity