Block #73,384,129

← previous blocknext block →recent activity

Analyzing

Block #73,384,129

12 transactions · 11 stateful · 2026-05-09 04:20:14 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,384,129  ·  12 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

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x75ebb92a…91a7

0x34b655…2a6f

4 touches
1 conflict

0x8a2657f5…e008

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf882d8d1…c9c7

0x34b655…2a6f

4 touches
1 conflict

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0x388f889f…a655

0x34b655…2a6f

2 touches
0 conflicts

0x64461c10…e86d

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 0x408e66bba7…d43d6b

← previous block·next block →recent activity