← previous blocknext block →recent activity

Analyzing

Block #72,288,081

30 transactions · 24 stateful · 2026-05-04 02:41:09 UTC

Parallelism

70/100

Blocked

63%

Avg conflicts / tx

1.5

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,288,081  ·  30 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

18 touches
36 conflicts

0x207c32d3…d39b

0x34b655…2a6f

6 touches
3 conflicts

0x220f4f84…15f8

0x34b655…2a6f

6 touches
3 conflicts

0x32ee90db…decc

0x34b655…2a6f

6 touches
3 conflicts

0x475d29e4…3caf

0x34b655…2a6f

6 touches
3 conflicts

0x52aeabb0…482b

0x34b655…2a6f

6 touches
3 conflicts

0x629e09e5…692a

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity