Block #72,498,046

← previous blocknext block →recent activity

Analyzing

Block #72,498,046

7 transactions · 7 stateful · 2026-05-05 02:00:15 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,498,046  ·  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

0x94eaf7ec…6dca

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe9a66bfa…4c29

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x936fdcd7…a0c1

0x065c9d…c394

2 touches
0 conflicts

0xa810b01c…31f0

0x065c9d…c394

2 touches
0 conflicts

0xbfc2969c…3077

0x065c9d…c394

2 touches
0 conflicts

0xf12417cb…d4b0

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 0x94eaf7ec08…aa6dca

← previous block·next block →recent activity