Block #73,359,126

← previous blocknext block →recent activity

Analyzing

Block #73,359,126

11 transactions · 10 stateful · 2026-05-09 01:33:54 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,359,126  ·  11 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

0xfdd131fa…dbdb

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0xd563f3a1…94b1

0x34b655…2a6f

4 touches
1 conflict

0x56eb2a24…60e1

0x34b655…2a6f

2 touches
0 conflicts

0x7dfcba82…fb68

0x34b655…2a6f

2 touches
0 conflicts

0x8d664414…3344

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 0xfdd131fae1…f8dbdb

← previous block·next block →recent activity