Block #72,429,740

← previous blocknext block →recent activity

Analyzing

Block #72,429,740

30 transactions · 23 stateful · 2026-05-04 18:25:21 UTC

Parallelism

80/100

Blocked

57%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,429,740  ·  30 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x1f0aadea…693d

0xd32edf…ff58

11 touches
15 conflicts

0xb245fe36…d765

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

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

15 conflicts on slot 0x1f0aadea8d…9f693d

← previous block·next block →recent activity