Block #72,283,163

← previous blocknext block →recent activity

Analyzing

Block #72,283,163

29 transactions · 22 stateful · 2026-05-04 02:08:03 UTC

Parallelism

69/100

Blocked

64%

Avg conflicts / tx

1.55

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,283,163  ·  29 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0x12bc0d2c…1c12

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0xaa3492db…3703

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity