← previous blocknext block →recent activity

Analyzing

Block #72,288,080

26 transactions · 19 stateful · 2026-05-04 02:41:09 UTC

Parallelism

85/100

Blocked

47%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,288,080  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe74ad3af…6373

0xd32edf…ff58

7 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x09beabbc…065c

0x188d58…ea8e

6 touches
3 conflicts

0x09beabbc…065d

0x188d58…ea8e

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…0018

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 0xe74ad3af66…636373

← previous block·next block →recent activity