← previous blocknext block →recent activity

Analyzing

Block #72,399,092

29 transactions · 19 stateful · 2026-05-04 15:01:10 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.93

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,399,092  ·  29 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

0xec1d6663…6042

0x34b655…2a6f

10 touches
10 conflicts

0x20ac0567…c954

0x34b655…2a6f

8 touches
6 conflicts

0x2484cc15…5afc

0x34b655…2a6f

8 touches
6 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

8 touches
6 conflicts

0x113e4acf…57fa

0x34b655…2a6f

8 touches
6 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity