← previous blocknext block →recent activity

Analyzing

Block #72,228,095

7 transactions · 6 stateful · 2026-05-03 19:57:56 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,228,095  ·  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

0xcea1a7d6…6eac

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb8c2438e…3ebd

0x065c9d…c394

3 touches
1 conflict

0x37f91cf5…14e0

0x065c9d…c394

3 touches
1 conflict

0x357e53cc…e772

0x065c9d…c394

2 touches
0 conflicts

0x97840a61…d833

0x065c9d…c394

2 touches
0 conflicts

0xe0d407ff…48ed

0x065c9d…c394

2 touches
0 conflicts

0xf8756adb…f761

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 0xcea1a7d690…3f6eac

← previous block·next block →recent activity