← previous blocknext block →recent activity

Analyzing

Block #72,285,732

38 transactions · 26 stateful · 2026-05-04 02:25:21 UTC

Parallelism

71/100

Blocked

65%

Avg conflicts / tx

1.16

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,285,732  ·  38 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd75d3994…363d

0xd32edf…ff58

15 touches
28 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x1df7f350…ee9a

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x872e51c8…ae25

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

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

28 conflicts on slot 0xd75d399489…1a363d

← previous block·next block →recent activity