Block #73,503,730

← previous blocknext block →recent activity

Analyzing

Block #73,503,730

7 transactions · 7 stateful · 2026-05-09 17:36:18 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,503,730  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7adfe561…c1e1

0x065c9d…c394

3 touches
1 conflict

0x0ee4515c…6af8

0x065c9d…c394

3 touches
1 conflict

0x6486390a…5022

0xd32edf…ff58

3 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0xc4ed8de0…d91b

0x065c9d…c394

2 touches
0 conflicts

0xd1f2ec8f…c7d9

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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