Block #72,399,253

← previous blocknext block →recent activity

Analyzing

Block #72,399,253

17 transactions · 12 stateful · 2026-05-04 15:02:14 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,399,253  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…0002

0x7e9d3a…9fda

10 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xefb03ae4…da55

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf023906c…2445

0x065c9d…c394

3 touches
1 conflict

0x9f37b594…f20f

0x065c9d…c394

3 touches
1 conflict

0x39e56c78…9be2

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0007

0x000000…1000

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: 0x7e9d3a8a…4f9fda

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity