Block #73,348,704

← previous blocknext block →recent activity

Analyzing

Block #73,348,704

14 transactions · 13 stateful · 2026-05-09 00:24:37 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,348,704  ·  14 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

0x42349dee…1c1e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x893cd52c…5766

0x34b655…2a6f

4 touches
1 conflict

0xdeaa385f…6b8b

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0f9b918b…212d

0x34b655…2a6f

4 touches
1 conflict

0xafd59af5…5257

0xc8689a…ee79

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

1 conflict on slot 0x42349deec1…d21c1e

← previous block·next block →recent activity