← previous blocknext block →recent activity

Analyzing

Block #72,496,278

12 transactions · 9 stateful · 2026-05-05 01:48:29 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,496,278  ·  12 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

0x0a79b808…ff9f

0x065c9d…c394

4 touches
1 conflict

0x591383f5…505b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9a77124b…1795

0x065c9d…c394

3 touches
1 conflict

0x25ab8c3d…c0cb

0x065c9d…c394

3 touches
1 conflict

0xc0924b50…c7fc

0x065c9d…c394

3 touches
1 conflict

0x9d9e5c3d…a207

0x065c9d…c394

3 touches
1 conflict

0x83e75a9f…5f0d

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 0x0a79b8085d…7dff9f

← previous block·next block →recent activity