Block #72,296,313

← previous blocknext block →recent activity

Analyzing

Block #72,296,313

26 transactions · 23 stateful · 2026-05-04 03:36:24 UTC

Parallelism

42/100

Blocked

61%

Avg conflicts / tx

3.35

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #72,296,313  ·  26 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0xe54a1f6f…18f2

0x34b655…2a6f

24 touches
66 conflicts

0xf853eb8e…4027

0x34b655…2a6f

20 touches
45 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

20 touches
45 conflicts

0xedb848fe…6534

0x34b655…2a6f

16 touches
28 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

16 touches
28 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

16 touches
28 conflicts

0x908d4442…2c4b

0x34b655…2a6f

16 touches
28 conflicts

0x9be2b99a…a959

0x34b655…2a6f

16 touches
28 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

66 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity