← previous blocknext block →recent activity

Analyzing

Block #72,425,489

16 transactions · 13 stateful · 2026-05-04 17:57:05 UTC

Parallelism

88/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,425,489  ·  16 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x317f6232…8a4c

0x065c9d…c394

4 touches
1 conflict

0xfbf2348a…b366

0x065c9d…c394

4 touches
1 conflict

0xc26c43c5…bf64

0x065c9d…c394

3 touches
1 conflict

0x2e9d0499…4cea

0x065c9d…c394

3 touches
1 conflict

0x89c51ead…025e

0x065c9d…c394

3 touches
1 conflict

0xbc445e6e…c71f

0x065c9d…c394

3 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

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 0x0000000000…00003d

← previous block·next block →recent activity