← previous blocknext block →recent activity

Analyzing

Block #72,285,681

28 transactions · 25 stateful · 2026-05-04 02:25:01 UTC

Parallelism

75/100

Blocked

64%

Avg conflicts / tx

1.32

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,285,681  ·  28 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

0xccbbc490…0078

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd59f6ed1…03e4

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

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

21 conflicts on slot 0xccbbc4906c…540078

← previous block·next block →recent activity