Block #72,283,840

← previous blocknext block →recent activity

Analyzing

Block #72,283,840

16 transactions · 14 stateful · 2026-05-04 02:12:37 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,283,840  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x1849a76a…cfdf

0x34b655…2a6f

4 touches
1 conflict

0x5f2e4654…3015

0x34b655…2a6f

4 touches
1 conflict

0x88915805…fbc9

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xdcf87d14…8825

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity