← previous blocknext block →recent activity

Analyzing

Block #72,300,834

7 transactions · 6 stateful · 2026-05-04 04:06:31 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,300,834  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x12535e11…b23c

0x065c9d…c394

4 touches
1 conflict

0x15bc6a8d…2e73

0x065c9d…c394

3 touches
1 conflict

0x401fda35…8d85

0x065c9d…c394

3 touches
1 conflict

0x8563e418…b4e3

0x065c9d…c394

2 touches
0 conflicts

0xa708f77b…ff5e

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xe251ab14…ad5b

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 0x0000000000…00003d

← previous block·next block →recent activity