Block #73,261,316

← previous blocknext block →recent activity

Analyzing

Block #73,261,316

22 transactions · 9 stateful · 2026-05-08 14:43:06 UTC

Parallelism

91/100

Blocked

22%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,261,316  ·  22 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…0002

0xab3526…fa38

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x62911ed0…3ff7

0x96b79e…d00a

2 touches
0 conflicts

0x8d3403c5…1fb1

0x96b79e…d00a

2 touches
0 conflicts

0x09106a95…1467

0xeedfbc…f7dc

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: 0xab35264b…1cfa38

1 conflict on slot 0x0000000000…000002

← previous block·next block →recent activity