← previous blocknext block →recent activity

Analyzing

Block #72,429,159

28 transactions · 24 stateful · 2026-05-04 18:21:28 UTC

Parallelism

75/100

Blocked

58%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,429,159  ·  28 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

0xadac4a86…c2bc

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x085df2c1…305a

0x34b655…2a6f

8 touches
6 conflicts

0x0b6d25a1…2e3b

0x34b655…2a6f

8 touches
6 conflicts

0x3c35979a…975d

0x34b655…2a6f

8 touches
6 conflicts

0x414e9446…4b59

0x34b655…2a6f

8 touches
6 conflicts

0x65e795ca…0320

0x34b655…2a6f

8 touches
6 conflicts

0x8aa1941d…2988

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

15 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity