Block #73,389,255

← previous blocknext block →recent activity

Analyzing

Block #73,389,255

10 transactions · 10 stateful · 2026-05-09 04:54:20 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,389,255  ·  10 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

0x51087f5a…61f7

0x34b655…2a6f

4 touches
1 conflict

0x8d664414…3344

0x34b655…2a6f

4 touches
1 conflict

0xaaa09a9b…4fed

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x746bcce3…d0ce

0x34b655…2a6f

2 touches
0 conflicts

0x95e5ee51…5e3e

0x34b655…2a6f

2 touches
0 conflicts

0xa9988419…9f45

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 0x51087f5abf…f061f7

← previous block·next block →recent activity