Block #73,651,998

← previous blocknext block →recent activity

Analyzing

Block #73,651,998

20 transactions · 17 stateful · 2026-05-10 10:04:36 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,651,998  ·  20 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

0x354a024c…1d41

0xd32edf…ff58

7 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x1c476c8d…bb49

0x065c9d…c394

4 touches
1 conflict

0x38524fae…9deb

0x34b655…2a6f

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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

6 conflicts on slot 0x354a024cb0…481d41

← previous block·next block →recent activity