Block #72,271,772

← previous blocknext block →recent activity

Analyzing

Block #72,271,772

39 transactions · 32 stateful · 2026-05-04 00:51:31 UTC

Parallelism

69/100

Blocked

59%

Avg conflicts / tx

1.41

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #72,271,772  ·  39 txs across 12 waves  ·  depth 12
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

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

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

10 touches
10 conflicts

0x085df2c1…305a

0x34b655…2a6f

8 touches
6 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

8 touches
6 conflicts

0x2877f440…c2c8

0x34b655…2a6f

8 touches
6 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x37379933…2402

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity