Block #72,285,921

← previous blocknext block →recent activity

Analyzing

Block #72,285,921

10 transactions · 9 stateful · 2026-05-04 02:26:37 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,285,921  ·  10 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

0xe3cc63ba…966d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe6c5b8a7…1e72

0x065c9d…c394

3 touches
1 conflict

0x10c8ba6a…be46

0x065c9d…c394

2 touches
0 conflicts

0x24d866cf…b001

0x065c9d…c394

2 touches
0 conflicts

0x5b4152ac…255f

0x065c9d…c394

2 touches
0 conflicts

0x753e1790…8a4d

0x065c9d…c394

2 touches
0 conflicts

0xa7cc43e5…d2e5

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 0xe3cc63ba4a…ac966d

← previous block·next block →recent activity