Block #73,660,734

← previous blocknext block →recent activity

Analyzing

Block #73,660,734

27 transactions · 18 stateful · 2026-05-10 11:03:29 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,660,734  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0fbd4084…1c3c

0xd32edf…ff58

13 touches
21 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x3964be9e…cf49

0x065c9d…c394

3 touches
1 conflict

0xdbebcc1c…bb95

0x065c9d…c394

3 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

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: 0xd32edf66…9fff58

21 conflicts on slot 0x0fbd408431…e31c3c

← previous block·next block →recent activity