Block #72,233,342

← previous blocknext block →recent activity

Analyzing

Block #72,233,342

7 transactions · 6 stateful · 2026-05-03 20:33:15 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,233,342  ·  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

0x796a44fd…4ed8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4443062d…77bd

0x065c9d…c394

4 touches
1 conflict

0xca5983db…6fc2

0x065c9d…c394

3 touches
1 conflict

0xc7653271…572d

0x065c9d…c394

3 touches
1 conflict

0x7d140af3…bd9e

0x065c9d…c394

3 touches
1 conflict

0x5728dca5…734e

0x065c9d…c394

3 touches
1 conflict

0x1a4b4152…0a08

0x8d0464…4402

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 0x796a44fd2c…6b4ed8

← previous block·next block →recent activity