← previous blocknext block →recent activity

Analyzing

Block #72,287,959

12 transactions · 11 stateful · 2026-05-04 02:40:20 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,287,959  ·  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

0x0fdfe9da…4d77

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x480e16fc…e2a4

0x065c9d…c394

3 touches
1 conflict

0x49c7a64d…e716

0x065c9d…c394

3 touches
1 conflict

0x52279c04…96fb

0x065c9d…c394

3 touches
1 conflict

0x6ae53523…2c70

0x065c9d…c394

3 touches
1 conflict

0x6ab5f622…5ce9

0x065c9d…c394

3 touches
1 conflict

0xb20eae18…f166

0x065c9d…c394

3 touches
1 conflict

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 0x0fdfe9da72…4b4d77

← previous block·next block →recent activity