Block #72,394,725

← previous blocknext block →recent activity

Analyzing

Block #72,394,725

22 transactions · 20 stateful · 2026-05-04 14:32:03 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,394,725  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0xc7f750ce…6f06

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity