← previous blocknext block →recent activity

Analyzing

Block #72,288,057

31 transactions · 27 stateful · 2026-05-04 02:41:00 UTC

Parallelism

77/100

Blocked

67%

Avg conflicts / tx

1.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,288,057  ·  31 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe50b5050…751d

0xd32edf…ff58

13 touches
21 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x1b8539d4…c57c

0x34b655…2a6f

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

6 touches
3 conflicts

0x41d020bb…22e6

0x34b655…2a6f

6 touches
3 conflicts

0x46bab9b1…ec16

0x34b655…2a6f

6 touches
3 conflicts

0x49486b48…c46b

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