Block #72,209,409

← previous blocknext block →recent activity

Analyzing

Block #72,209,409

10 transactions · 9 stateful · 2026-05-03 17:52:25 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,209,409  ·  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

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x4412c608…40c0

0x065c9d…c394

2 touches
0 conflicts

0x68c031cd…5b84

0x065c9d…c394

2 touches
0 conflicts

0xb0be8456…198c

0x065c9d…c394

2 touches
0 conflicts

0xd2b1a788…05db

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: 0x34b6552d…112a6f

1 conflict on slot 0x388f889f28…0aa655

← previous block·next block →recent activity