Block #72,497,000

← previous blocknext block →recent activity

Analyzing

Block #72,497,000

34 transactions · 29 stateful · 2026-05-05 01:53:17 UTC

Parallelism

74/100

Blocked

62%

Avg conflicts / tx

1.71

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,497,000  ·  34 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xc4cd440e…968c

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x7b8a46eb…a3c4

0x065c9d…c394

4 touches
1 conflict

0x1c354dc0…96de

0x754704…b603

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

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

36 conflicts on slot 0xc4cd440e00…56968c

← previous block·next block →recent activity