Block #72,974,615

← previous blocknext block →recent activity

Analyzing

Block #72,974,615

17 transactions · 13 stateful · 2026-05-07 06:55:32 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0x065c9d…c394

8 touches
6 conflicts

0x70b2f813…783c

0x2a68ba…90c5

6 touches
3 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0xa61f847c…e2ee

0x065c9d…c394

4 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x0175b7a6…1dbb

0x6ca43f…c331

4 touches
1 conflict

0x0175b7a6…1dbd

0x6ca43f…c331

4 touches
1 conflict

0x1a4b4152…0a08

0x6ca43f…c331

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity