Block #72,496,969

← previous blocknext block →recent activity

Analyzing

Block #72,496,969

12 transactions · 11 stateful · 2026-05-05 01:53:05 UTC

Parallelism

42/100

Blocked

64%

Avg conflicts / tx

1.67

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,496,969  ·  12 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xff5222e8…3686

0xd32edf…ff58

11 touches
15 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x3e6a8ff9…75b2

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xd996735f…8732

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xd9f18d9a…141d

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 0xff5222e80f…843686

← previous block·next block →recent activity