Block #73,338,067

← previous blocknext block →recent activity

Analyzing

Block #73,338,067

7 transactions · 6 stateful · 2026-05-08 23:13:51 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,338,067  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4f91fd62…d68e

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x8a7d366e…60af

0x065c9d…c394

3 touches
1 conflict

0xca9e84d6…bc94

0x065c9d…c394

3 touches
1 conflict

0x6bd9b2de…7d72

0x0f2610…0edc

2 touches
0 conflicts

0xe4666cf4…3463

0x2185cd…21c7

2 touches
0 conflicts

0xd2096861…b7b2

0x2ae0cf…3d4e

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 0x0000000000…00003d

← previous block·next block →recent activity