Block #72,301,057

← previous blocknext block →recent activity

Analyzing

Block #72,301,057

8 transactions · 5 stateful · 2026-05-04 04:08:00 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,057  ·  8 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

0x7c759cc5…8525

0x065c9d…c394

4 touches
1 conflict

0x12535e11…b23c

0x065c9d…c394

4 touches
1 conflict

0x6babf30d…e57e

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x51e09591…69a8

0x065c9d…c394

3 touches
1 conflict

0xf7749614…0c9f

0x065c9d…c394

3 touches
1 conflict

0xfe096b48…37d9

0x065c9d…c394

3 touches
1 conflict

0x419b2d5b…7419

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

1 conflict on slot 0x7c759cc562…598525

← previous block·next block →recent activity