← previous blocknext block →recent activity

Analyzing

Block #72,400,202

11 transactions · 9 stateful · 2026-05-04 15:08:34 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,400,202  ·  11 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

0x7bdc89f2…eaec

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfb9471f9…1e42

0x065c9d…c394

3 touches
1 conflict

0xb70c3643…0e6a

0x065c9d…c394

3 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0xf93a2b29…dd13

0x065c9d…c394

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

2 touches
0 conflicts

0xbf04f37d…85f2

0x2a68ba…90c5

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 0x7bdc89f2a3…97eaec

← previous block·next block →recent activity