← previous blocknext block →recent activity

Analyzing

Block #72,430,979

9 transactions · 7 stateful · 2026-05-04 18:33:36 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,430,979  ·  9 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

0xcf41bef6…b6fd

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x100b63d7…b01c

0x065c9d…c394

3 touches
1 conflict

0x9cbd06cf…f487

0x065c9d…c394

3 touches
1 conflict

0x6a8380a2…72d3

0x065c9d…c394

2 touches
0 conflicts

0xd40df93d…3d75

0x065c9d…c394

2 touches
0 conflicts

0xddc823c9…aca9

0x065c9d…c394

2 touches
0 conflicts

0xdfecbfbf…7736

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 0xcf41bef6c3…6fb6fd

← previous block·next block →recent activity