Block #72,974,597

← previous blocknext block →recent activity

Analyzing

Block #72,974,597

18 transactions · 16 stateful · 2026-05-07 06:55:25 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,974,597  ·  18 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…003d

0x065c9d…c394

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0x70b2f813…783c

0x2a68ba…90c5

8 touches
6 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

8 touches
6 conflicts

0x1c3af45b…416e

0x6ca43f…c331

8 touches
6 conflicts

0x3e4b8d9f…b8a7

0x6ca43f…c331

8 touches
6 conflicts

0xc5564f8e…f4bf

0x6ca43f…c331

8 touches
6 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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity