Block #72,429,279

← previous blocknext block →recent activity

Analyzing

Block #72,429,279

13 transactions · 10 stateful · 2026-05-04 18:22:16 UTC

Parallelism

69/100

Blocked

40%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,429,279  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x7eeb9792…3604

0xc8689a…ee79

4 touches
1 conflict

0x8ffcccd9…df64

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf7b100db…087d

0x065c9d…c394

3 touches
1 conflict

0x61e84d51…25d7

0x065c9d…c394

3 touches
1 conflict

0x2c0fa1d3…c349

0x065c9d…c394

3 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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity