Block #73,500,044

← previous blocknext block →recent activity

Analyzing

Block #73,500,044

6 transactions · 6 stateful · 2026-05-09 17:11:41 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x468c69b1…af11

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x23951077…539b

0x34b655…2a6f

2 touches
0 conflicts

0x5728edaf…f1d4

0x34b655…2a6f

2 touches
0 conflicts

0x578e7f66…1b56

0x34b655…2a6f

2 touches
0 conflicts

0x57de3828…3fbb

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: 0x8d66a43f…113095

1 conflict on slot 0x468c69b112…86af11

← previous block·next block →recent activity