Block #72,429,208

← previous blocknext block →recent activity

Analyzing

Block #72,429,208

19 transactions · 16 stateful · 2026-05-04 18:21:48 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,429,208  ·  19 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

0x6754d853…5681

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x6aa624fd…a84e

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

6 conflicts on slot 0x6754d85396…715681

← previous block·next block →recent activity