Block #72,429,543

← previous blocknext block →recent activity

Analyzing

Block #72,429,543

28 transactions · 20 stateful · 2026-05-04 18:24:02 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.68

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,429,543  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xe411cce0…3989

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x083a8763…5a7b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

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

45 conflicts on slot 0xe411cce00e…ee3989

← previous block·next block →recent activity