Block #73,492,326

← previous blocknext block →recent activity

Analyzing

Block #73,492,326

7 transactions · 6 stateful · 2026-05-09 16:20:22 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,492,326  ·  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

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x37cfaf01…4a46

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0334d556…ea99

0x065c9d…c394

2 touches
0 conflicts

0x1ba9c278…effe

0x065c9d…c394

2 touches
0 conflicts

0x3411376c…6f0a

0x065c9d…c394

2 touches
0 conflicts

0x682d342e…6ccf

0x065c9d…c394

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 0x6eba5e7f6a…ac4b52

← previous block·next block →recent activity