Block #72,224,610

← previous blocknext block →recent activity

Analyzing

Block #72,224,610

20 transactions · 18 stateful · 2026-05-03 19:34:31 UTC

Parallelism

65/100

Blocked

39%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,224,610  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd690157b…6872

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xa6331f0c…3055

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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: 0xd32edf66…9fff58

21 conflicts on slot 0xd690157bc9…676872

← previous block·next block →recent activity