Block #72,501,121

← previous blocknext block →recent activity

Analyzing

Block #72,501,121

10 transactions · 10 stateful · 2026-05-05 02:20:43 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,501,121  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0f2fbb56…9c57

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0733ff0d…580a

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x71e184c3…2e5d

0x065c9d…c394

2 touches
0 conflicts

0xab171640…02b9

0x065c9d…c394

2 touches
0 conflicts

0xc0988fc9…e12e

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

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

1 conflict on slot 0x0f2fbb56b8…749c57

← previous block·next block →recent activity