Block #73,384,036

← previous blocknext block →recent activity

Analyzing

Block #73,384,036

17 transactions · 16 stateful · 2026-05-09 04:19:37 UTC

Parallelism

76/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,384,036  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xe038916c…b1be

0x2a68ba…90c5

4 touches
1 conflict

0x0d58ee92…a6b5

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xda6b535e…6d6d

0x1b6862…e19c

4 touches
1 conflict

0xb0e2f9aa…4c3e

0xd32edf…ff58

3 touches
1 conflict

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

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity