← previous blocknext block →recent activity

Analyzing

Block #72,282,997

17 transactions · 15 stateful · 2026-05-04 02:06:56 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,282,997  ·  17 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

0x2be23fc1…60a3

0xd32edf…ff58

9 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

5 touches
3 conflicts

0x143dba04…1b98

0x8d66a4…3095

5 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

10 conflicts on slot 0x2be23fc180…9c60a3

← previous block·next block →recent activity