Block #72,365,974

← previous blocknext block →recent activity

Analyzing

Block #72,365,974

31 transactions · 22 stateful · 2026-05-04 11:20:25 UTC

Parallelism

65/100

Blocked

64%

Avg conflicts / tx

1.45

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,365,974  ·  31 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

0x1c913164…5c2e

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xdf889704…8950

0x34b655…2a6f

10 touches
10 conflicts

0xedb848fe…6534

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0x629480fc…7d2f

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0x1c913164f5…845c2e

← previous block·next block →recent activity