Block #72,500,979

← previous blocknext block →recent activity

Analyzing

Block #72,500,979

7 transactions · 7 stateful · 2026-05-05 02:19:46 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,500,979  ·  7 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

0x67822b7c…4860

0x065c9d…c394

4 touches
1 conflict

0x3b8701a9…1f34

0x065c9d…c394

3 touches
1 conflict

0xed6de5ec…7591

0x065c9d…c394

3 touches
1 conflict

0x618af8f5…ba1a

0x065c9d…c394

2 touches
0 conflicts

0x8cb4260e…2ff5

0x065c9d…c394

2 touches
0 conflicts

0xc6113171…6369

0x065c9d…c394

2 touches
0 conflicts

0xf6b1ae19…6094

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

← previous block·next block →recent activity