Block #72,288,490

← previous blocknext block →recent activity

Analyzing

Block #72,288,490

36 transactions · 30 stateful · 2026-05-04 02:43:53 UTC

Parallelism

75/100

Blocked

60%

Avg conflicts / tx

1.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,288,490  ·  36 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

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0xbb975a6c…bff4

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf2ef21a4…599c

0x34b655…2a6f

8 touches
6 conflicts

0x7cb2f3fa…4836

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity