Block #73,640,589

← previous blocknext block →recent activity

Analyzing

Block #73,640,589

10 transactions · 8 stateful · 2026-05-10 08:47:49 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,640,589  ·  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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

3 touches
1 conflict

0x03924cd3…f268

0x8d66a4…3095

3 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

3 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x2d6d9781…f1fa

0x34b655…2a6f

2 touches
0 conflicts

0x99d5ffa1…4059

0x34b655…2a6f

2 touches
0 conflicts

0xad0fa15c…e45b

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity