Block #72,172,348

← previous blocknext block →recent activity

Analyzing

Block #72,172,348

18 transactions · 8 stateful · 2026-05-03 13:43:25 UTC

Parallelism

89/100

Blocked

38%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,172,348  ·  18 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x06dfe687…a8db

0x065c9d…c394

3 touches
1 conflict

0xec149ca4…7314

0xd32edf…ff58

3 touches
1 conflict

0x4c93193c…f061

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xafb02507…f83c

0x065c9d…c394

2 touches
0 conflicts

0xb54d55bd…c8a7

0x065c9d…c394

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 0x0000000000…00003d

← previous block·next block →recent activity