← previous blocknext block →recent activity

Analyzing

Block #72,430,964

18 transactions · 15 stateful · 2026-05-04 18:33:30 UTC

Parallelism

78/100

Blocked

60%

Avg conflicts / tx

0.83

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,430,964  ·  18 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

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x4d42f16e…a6c9

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

6 touches
3 conflicts

0x6ef3176f…15df

0xd32edf…ff58

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