← previous blocknext block →recent activity

Analyzing

Block #72,575,434

16 transactions · 14 stateful · 2026-05-05 10:35:32 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,575,434  ·  16 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x7eeb9792…3604

0xc8689a…ee79

6 touches
3 conflicts

0x95bda0ff…7130

0x065c9d…c394

6 touches
3 conflicts

0xd393a3d0…4b6c

0x065c9d…c394

6 touches
3 conflicts

0x2e2214a9…fe0d

0x8d0464…4402

6 touches
3 conflicts

0xf0f673fd…37a7

0x8d0464…4402

6 touches
3 conflicts

0x50997ada…364d

0x8d0464…4402

5 touches
3 conflicts

0xc5564f8e…f4bf

0x8d0464…4402

5 touches
3 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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity