Block #73,660,704

← previous blocknext block →recent activity

Analyzing

Block #73,660,704

11 transactions · 9 stateful · 2026-05-10 11:03:17 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,660,704  ·  11 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…003d

0x065c9d…c394

8 touches
6 conflicts

0x2175e234…efbb

0x065c9d…c394

4 touches
1 conflict

0x36fcdcb5…3f95

0x065c9d…c394

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0xa8e08ae8…b7f9

0x065c9d…c394

4 touches
1 conflict

0xb73bcea3…96b9

0x065c9d…c394

4 touches
1 conflict

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6c4bfa…a540

4 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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity