Block #72,301,258

← previous blocknext block →recent activity

Analyzing

Block #72,301,258

9 transactions · 7 stateful · 2026-05-04 04:09:21 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,258  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xbbad5c01…454e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x1608635c…d25d

0x34b655…2a6f

2 touches
0 conflicts

0x21756df9…567d

0x34b655…2a6f

2 touches
0 conflicts

0x2fc166fd…c38a

0x34b655…2a6f

2 touches
0 conflicts

0x323c931a…a50c

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xbbad5c01bb…4c454e

← previous block·next block →recent activity