Block #72,399,281

← previous blocknext block →recent activity

Analyzing

Block #72,399,281

30 transactions · 17 stateful · 2026-05-04 15:02:25 UTC

Parallelism

83/100

Blocked

47%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,399,281  ·  30 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xec1d6663…6042

0x34b655…2a6f

6 touches
3 conflicts

0x3c170160…d3c9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0xc1baef71…0689

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

4 touches
1 conflict

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

← previous block·next block →recent activity