Block #72,288,424

← previous blocknext block →recent activity

Analyzing

Block #72,288,424

36 transactions · 26 stateful · 2026-05-04 02:43:26 UTC

Parallelism

64/100

Blocked

69%

Avg conflicts / tx

2.53

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #72,288,424  ·  36 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x6d693016…cf61

0xd32edf…ff58

25 touches
78 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21bf

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xbfde9215…4148

0x065c9d…c394

7 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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

78 conflicts on slot 0x6d6930165f…facf61

← previous block·next block →recent activity