Block #73,744,424

← previous blocknext block →recent activity

Analyzing

Block #73,744,424

7 transactions · 6 stateful · 2026-05-10 20:28:15 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,744,424  ·  7 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

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x6135d9cb…d849

0x065c9d…c394

2 touches
0 conflicts

0x8d8fc7ca…0205

0x065c9d…c394

2 touches
0 conflicts

0xa1f67e2b…fa1c

0x065c9d…c394

2 touches
0 conflicts

0xad5e269a…89ad

0x065c9d…c394

2 touches
0 conflicts

0xe6349cc7…0f51

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity