Block #73,500,357

← previous blocknext block →recent activity

Analyzing

Block #73,500,357

7 transactions · 6 stateful · 2026-05-09 17:13:46 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,500,357  ·  7 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

0x2fad73a1…ae09

0x34b655…2a6f

4 touches
1 conflict

0xfe39a1f7…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x3a429191…9cda

0x34b655…2a6f

2 touches
0 conflicts

0x5b1c722b…3332

0x34b655…2a6f

2 touches
0 conflicts

0x67365c5c…b53a

0x34b655…2a6f

2 touches
0 conflicts

0x89999c15…fdac

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 0x2fad73a1ce…31ae09

← previous block·next block →recent activity