← previous blocknext block →recent activity

Analyzing

Block #72,366,277

14 transactions · 13 stateful · 2026-05-04 11:22:26 UTC

Parallelism

50/100

Blocked

54%

Avg conflicts / tx

1.36

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,366,277  ·  14 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

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

10 touches
10 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x8aa1941d…2988

0x34b655…2a6f

6 touches
3 conflicts

0xa8bd52b5…862e

0x34b655…2a6f

6 touches
3 conflicts

0xb6aedce9…a483

0x34b655…2a6f

6 touches
3 conflicts

0xd94b6f7c…65f0

0x34b655…2a6f

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: 0x34b6552d…112a6f

10 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity