Block #72,288,140

← previous blocknext block →recent activity

Analyzing

Block #72,288,140

31 transactions · 23 stateful · 2026-05-04 02:41:33 UTC

Parallelism

61/100

Blocked

52%

Avg conflicts / tx

1.39

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #72,288,140  ·  31 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

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

12 touches
15 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xf11f3c3f…1734

0x34b655…2a6f

8 touches
6 conflicts

0x943e9fce…3cdb

0x34b655…2a6f

6 touches
3 conflicts

0x99f080dc…58c1

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity