← previous blocknext block →recent activity

Analyzing

Block #72,233,867

32 transactions · 23 stateful · 2026-05-03 20:36:45 UTC

Parallelism

88/100

Blocked

43%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,233,867  ·  32 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6c883bfb…d54e

0xd32edf…ff58

7 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x005fb969…2d97

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 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: 0xd32edf66…9fff58

6 conflicts on slot 0x6c883bfb95…f8d54e

← previous block·next block →recent activity